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

Is the Mistic Backdoor Hiding in Your Security Tools?

Introduction The emergence of the Mistic backdoor represents a sophisticated advancement in the arsenal of modern cybercriminals, specifically those operating within the niche of Initial Access Brokering (IAB). This malicious software, also identified by some security researchers as MLTBackdoor, has been actively infiltrating corporate environments throughout the first half of 2026. Its primary strength lies in its ability to camouflage

Is the Redmi 17C the New King of Budget Smartphones?

Dominic Jainy is a seasoned IT professional with a deep understanding of how hardware evolution impacts the budget mobile market. Today, he breaks down Xiaomi’s latest strategic move with the Redmi 17C, a device that surprisingly leaps over a generation to deliver high-refresh-rate displays and massive battery life to the entry-level segment. We explore the balance between essential utility features,

How Can PowerTool Speed Up Business Central Data Migrations?

Modern enterprises frequently encounter significant friction during ERP transitions because traditional data migration methods often fail to accommodate the sheer volume and complexity of contemporary datasets. In 2026, the demand for agility within Microsoft Dynamics 365 Business Central has reached a point where standard configuration packages, while functional for small tasks, often act as a bottleneck for larger implementations. The

How to Move Beyond the Portal to a True Developer Platform?

Dominic Jainy stands at the forefront of the modern cloud-native movement, possessing a deep technical mastery of artificial intelligence, machine learning, and blockchain architectures. With years of experience navigating the complexities of large-scale IT infrastructures, he has become a leading voice in the evolution of platform engineering. His perspective is shaped by the practical realities of moving beyond simple automation

Will AI Token Costs Soon Surpass Developer Salaries?

Recent financial projections indicate that the cost of maintaining high-frequency artificial intelligence interactions is rapidly approaching the median annual compensation of experienced software engineers in the global market. As the software development industry undergoes a radical transformation, the traditional overhead associated with human labor is being challenged by the sheer volume of data processed through large language models. This shift