Why Intel’s Spectre Fixes Sparked Linus Torvalds’ Fury and System Chaos

Intel CPU Design Vulnerabilities Exposed

On January 2, 2018, Intel disclosed a critical CPU design flaw that later became known as the Spectre and Meltdown vulnerabilities.

The disclosure sparked immediate reactions from hardware manufacturers, operating‑system vendors, and cloud providers, who faced the choice of fixing the issue at the hardware level or applying costly OS‑level mitigations, potentially even replacing affected CPUs.

Linus Torvalds’ Strong Opposition

By January 22, media reports highlighted that Linux patches intended to mitigate Spectre were causing frequent crashes. Linus Torvalds publicly denounced Intel’s Spectre fix as “complete and utter garbage,” accusing Intel of providing ineffective patches.

Torvalds also criticized Intel for refusing to acknowledge the CPU problems and for releasing PR statements that downplayed the issue.

“IBRS is complete garbage.”

In a discussion with Amazon engineer David Woodhouse, Torvalds explained that the release of Linux Kernel 4.15 was delayed due to unfinished network fixes and a minor boot error recently addressed by Laura Abbott.

Critique of IBRS and Redundant Patches

Torvalds argued that Intel’s indirect branch restricted speculation (IBRS) feature dramatically reduces system performance and that Intel has not enabled it because of the severe overhead, effectively shifting the blame to users.

He emphasized that the primary focus should be on fixing the Meltdown vulnerability rather than applying blanket patches, noting that techniques like Google’s “retpoline” already mitigate the issue.

According to Torvalds, the additional patches are unnecessary, increase complexity, and make the overall mitigation strategy less effective.

Widespread Patch‑Related Problems

Torvalds is not alone in his frustration. Early in the month, Red Hat released updates containing Intel microcode for Spectre that caused severe performance degradation and even prevented systems from booting, forcing a rollback. Ubuntu experienced similar issues.

Windows updates for Spectre and Meltdown also caused boot failures on AMD Opteron, Athlon, and Turion X2 Ultra CPUs, leading to temporary retractions.

Intel’s Request to Pause Updates

Intel issued a statement acknowledging partner feedback and confirming ongoing collaboration with the Linux community to find a solution.

Navin Shenoy, Intel’s Data Center VP, announced that the Broadwell and Haswell platforms were experiencing frequent reboots due to the patches and advised OEMs, system integrators, cloud providers, and users to pause applying the security updates while a new patch is tested and expected to be released by the end of the week.

Intel maintains a dedicated page for the two major security flaws, regularly updating it with new announcements, vulnerability analyses, and performance impact tests.

Until the forthcoming patch is released, Intel recommends that users refrain from applying older security updates to avoid system instability.