Torvalds Slams Intel, AMD, NVIDIA for Faulty Hardware Causing Linux Issues

Linux’s creator, Linus Torvalds, has taken a strong stance against major hardware manufacturers, voicing his dissatisfaction with Intel, AMD, and NVIDIA. He blames these companies for causing various vulnerabilities in the Linux operating system due to what he describes as "buggy hardware." Torvalds has repeatedly pointed out that these hardware flaws necessitate numerous modifications to the Linux kernel to guard against theoretical attacks that, in his view, rarely manifest in practical scenarios. This extensive burden falls on the Linux development community, who have to spend considerable time and resources addressing issues they didn’t create.

Torvalds’s Frustrations with CPU Vulnerabilities

One of the most prominent issues Torvalds has highlighted involves new CPUs from companies like Intel, which require significant kernel modifications to counteract vulnerabilities. A specific point of contention is the Linear Address Masking (LAM) feature in Intel CPUs intended to ensure memory integrity through a pointer-based implementation. However, this feature has led to speculation attacks known as SLAM. These vulnerabilities, according to Torvalds, should be the responsibility of the hardware manufacturers to fix, not the software developers.

Torvalds’s argument underscores his frustration with the additional workload placed on Linux developers, who must implement these fixes to guard against theoretical flaws. These modifications are seen as an unnecessary diversion of resources, detracting from more impactful development projects. This ongoing situation illustrates a broader problem within the industry, where hardware-related vulnerabilities significantly impact software stability and security.

Intel’s Response and the Future Mitigations

An Intel engineer responded to Torvalds’s concerns about the LAM vulnerabilities, stating that the functionality was supposed to be disabled until security vulnerabilities were resolved. The engineer suggested that potential attacks related to LAM would eventually be mitigated by another feature known as Linear Address Space Separation (LASS), though the fix for LASS has yet to be released. This interim period leaves the Linux community grappling with the flaws until a permanent solution is implemented.

The delay in releasing the LASS fix has only fueled the frustration among Linux developers, who find themselves continuously addressing these hardware-induced vulnerabilities. This is not just an isolated incident but rather a recurring issue that has led to increased workload and resource diversion. The consistent need for kernel modifications not only taxes the development community but also affects the overall stability and security of the Linux operating system.

Clashes Over AMD’s fTPM Feature

Torvalds’s discontent is not limited to Intel; he has also criticized AMD over its Firmware Trusted Platform Module (fTPM) feature. He argues that fTPM should not be run at runtime due to its propensity to cause bugs and crashes. In previous instances, Torvalds has demanded that AMD disable this feature to prevent these issues from impacting system stability. The problematic fTPM functionality has been a persistent thorn in the side of Linux developers.

The necessity to implement complex workarounds to maintain system stability due to fTPM’s issues underscores a broader problem of hardware manufacturers introducing features without fully considering their implications for operating system integrity. This ongoing tension reveals a significant disconnect between hardware design and software requirements, further complicating the task of maintaining a stable and secure Linux environment.

NVIDIA: The Unmentioned Grievances

While Torvalds’s criticisms of Intel and AMD are well-documented, his grievances with NVIDIA remain less specific in this discussion. However, NVIDIA’s reputation for causing headaches in the Linux community is a well-known issue. The dissatisfaction likely stems from similar problems plaguing Intel and AMD hardware—vulnerabilities and bugs that require excessive kernel modifications and divert resources from more valuable development tasks.

The general sentiment within the Linux development community is that NVIDIA’s hardware similarly introduces bugs and vulnerabilities that disproportionately burden Linux developers. This ongoing issue highlights the need for better hardware-software integration and more proactive measures from hardware manufacturers in addressing potential security flaws before they impact users.

The Call for Greater Accountability

At the core of Torvalds’s complaints is a call for greater accountability from hardware manufacturers. He strongly believes that these companies should take ownership of the vulnerabilities arising from their products. The Linux development community should not have to shoulder the responsibility of fixing hardware flaws that shouldn’t exist in the first place. Torvalds’s advocacy for a more responsible approach highlights the critical relationship between hardware and operating system integrity.

Torvalds’s push for accountability includes advocating for a shift in how these issues are managed, emphasizing that hardware manufacturers need to take more proactive steps in addressing vulnerabilities. By shedding light on the lack of accountability among hardware manufacturers, Torvalds is not only criticizing current practices but also pushing for systemic changes in how the tech industry handles security and stability issues.

The Broader Industry Trend

Torvalds’s call for greater accountability is reflective of a broader trend within the tech industry, where there is a growing consensus about the need for better collaboration between hardware manufacturers and software developers to tackle security vulnerabilities effectively. However, Torvalds’s message suggests that such collaboration is still lacking, with hardware manufacturers not shouldering enough of the burden. This gap in collaboration has wider implications for the tech community.

As new vulnerabilities emerge, the lack of effective teamwork between hardware and software developers can lead to increased security risks and slower innovation. Torvalds’s criticisms serve as a wake-up call for the industry to address these issues more proactively, highlighting the need for a more balanced approach towards handling vulnerabilities. The goal is to ensure a secure and efficient technological future by fostering better cooperation between both sides of the technology spectrum.

Impact on the Linux Development Community

Linux creator Linus Torvalds has been quite vocal in criticizing major hardware manufacturers, particularly targeting Intel, AMD, and NVIDIA. He holds these companies responsible for introducing various vulnerabilities into the Linux operating system through what he labels as "buggy hardware." Torvalds argues that these hardware imperfections force the Linux development team to make numerous adjustments to the Linux kernel to protect against theoretical attacks. In his view, these types of attacks are infrequent in real-world conditions, yet the community must dedicate immense time and resources to address these flaws. This has placed a heavy burden on Linux developers who end up having to fix problems they didn’t originate. Torvalds’ pointed remarks highlight his frustration with the ongoing need to tweak and safeguard the Linux OS continually. The implication is that if hardware makers improved their product quality, the Linux community could focus on enhancing the OS’s functionality rather than patching vulnerabilities.

Explore more

Ethereum Tests Glamsterdam Upgrade Amid Market Volatility

The activation of the Glamsterdam upgrade on the Sepolia testnet marks a critical phase in Ethereum’s infrastructure scaling as the network tests a gas limit increase from 60 million to 200 million. This substantial expansion of the gas limit represents a calculated gamble on the robustness of current hardware, aimed at accommodating a new wave of high-throughput decentralized applications. While

How to Design and Optimize AI Prompts for Production

The shift from experimental chatbots to high-scale enterprise intelligence systems in 2026 has transformed prompt engineering from a creative writing exercise into a disciplined branch of software engineering. The most effective production prompts use structural separation to distinguish between trusted system instructions and untrusted content from user inputs or retrieved documents. When an application processes thousands of model calls against

What Are the Best Email Marketing Tools for SMBs in 2026?

Small businesses often choose Constant Contact because it offers an extensive library of templates and specialized tools for managing event registrations and ticketing directly through emails. However, the broader landscape of digital outreach has shifted significantly, transforming email from a simple messaging tool into a sophisticated infrastructure for revenue growth and long-term customer retention. In 2026, the success of a

EY Breach Exposes Goldman Sachs and Man Group Client Data

Administrative IT tickets used for routine tax services inadvertently served as a repository for sensitive client data that was eventually stolen by hackers. This security failure at Ernst & Young (EY) has sent ripples through the financial sector, as it compromised the personal information of high-net-worth individuals associated with Goldman Sachs and the London-based hedge fund Man Group. While these

New Phishing Campaign Impersonates AI Tools to Steal MFA Codes

The campaign exploits the established trust that advertising agencies place in AI tools to bypass multi-factor authentication protocols that were previously considered secure. This sophisticated operation, identified in late 2026, represents a significant shift in the threat landscape, moving away from generic banking lures and toward the highly specialized tools used by modern marketing professionals. By impersonating platforms such as