Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Security Management //

Patch Management

1/24/2018
09:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Linus Torvalds: Intel's Spectre Patch Is 'Complete & Utter Garbage'

In a scathing assessment of Intel's efforts to patch the Spectre flaw, Linux inventor Linus Torvalds offers no quarter for the chipmaker.

The patching for Spectre isn't going well.

Earlier this week, Intel Corp. (Nasdaq: INTC) was forced to advise its customers -- that means OEMs, cloud service providers, system manufacturers, software vendors, end users, etc. -- to stop deployment of the Spectre patch and await further information. Unexpected system reboots were cited as the immediate cause, along with "other unpredictable system behavior."

Not only that, Linux inventor Linus Torvalds took to a Linux kernel mailing list on Sunday, January 21, to call Intel's approach to fixing Spectre "COMPLETE AND UTTER GARBAGE." (The capitalization for emphasis is his.)

Torvalds is OK with what Intel is doing for the Meltdown problem, however. (See New Intel Vulnerability Hits Almost Everyone.)

"The speculation control cpuid stuff shows that Intel actually seems to plan on doing the right thing for meltdown (the main question being _when_)," Torvalds wrote.

But the Spectre -- the branch target injection design flaw affecting most of its processor chips -- response causes him to ask: "WHAT THE F*CK IS GOING ON?"

Torvalds sees Intel playing games to make the benchmarks look better. As he puts it:

The whole IBRS_ALL feature to me very clearly says Intel is not serious about this, we'll have a ugly hack that will be so expensive that we don't want to enable it by default, because that would look bad in benchmarks.

Indirect Branch Restricted Speculation (IBRS) is the part of the patching that restricts speculation of indirect program branches.

Torvalds sums up his aversions by writing in the message that to him, the whole point of having CPUID and flags from the microarchitecture -- like IBRS_ALL -- is that they can be used make decisions.

However, since people already know that the IBRS overhead is very large on existing hardware, the hardware capability bits will be totally not useful. Torvalds thinks that "nobody sane will use them, since the cost is too damn high."

Torvalds does have a point here.

In its official position paper, Intel doesn't treat Spectre as a bug. Instead the chipmaker is offering Spectre protection as a feature. The company implicitly admits the vulnerability will be present in future CPUs, but it gives users an opt-in flag for their solution. This is the approach that Torvalds find abhorrent.

What Torvalds says that he wants is to see is some flag from the CPU saying that it has been fixed against Spectre, so that the OS does not have to impose its own fixes. He thinks the Spectre fix should be defaulted to on, regardless of the performance hit.

This stuff will remain a contentious area for a long time. Intel is getting tripped up by its rush to get a fix out the door, and not doing the validation that a major change of this magnitude needs. It also may have been influenced by liability issues implicit in the problem and trying to downplay just how serious the problem is to most of its customers.

In any case, it may serve users well to hold back on applying any patches that may result from this effort until they have been shown to be effective and do not cause instabilities of their own.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/2/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9498
PUBLISHED: 2020-07-02
Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed...
CVE-2020-3282
PUBLISHED: 2020-07-02
A vulnerability in the web-based management interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an unauthenticated, remote attack...
CVE-2020-5909
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, when users run the command displayed in NGINX Controller user interface (UI) to fetch the agent installer, the server TLS certificate is not verified.
CVE-2020-5910
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection would be authorized.
CVE-2020-5911
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.