Nvidia’s 4-Year Driver Bug Let One GPU Tenant Root the Host

Security firm Stealthium says two bugs in Nvidia’s Linux GPU driver, which it calls ForgePtr and NvRoot, let an unprivileged user on a shared GPU server take over the host. In its write-up, Stealthium says both have been in the driver “since its first open-source release in May 2022, more than four years ago”. Nvidia fixed them in its September 2026 security bulletin.

Our number: from May 2022 to the bulletin’s 30 September 2026 release is 52 months, about four years and four months, by our arithmetic. Nvidia scores both bugs 7.8, the highest score in that bulletin, which by our count lists 114 CVEs, 69 of them at 7.8.

Business Pill · Red Teaming

An evergreen Business Engineer explainer on red teaming, testing systems the way an attacker would. It teaches the general idea only and does not discuss these bugs.

The key insight: Stealthium says two bugs in Nvidia’s Linux GPU driver, ForgePtr and NvRoot, let an unprivileged user on a shared GPU server take over the host; both sat in the driver for about 52 months by our arithmetic before Nvidia’s September 2026 bulletin fixed them, and Nvidia scores each 7.8, the bulletin’s highest score.

What Stealthium Says the Bugs Do

Stealthium says ForgePtr (CVE-2026-47501) “starts with a missing error check and ends with an unprivileged write into kernel memory”. From there, the firm says, it “loaded an unsigned kernel module on a machine running Secure Boot”.

NvRoot (CVE-2026-47591), it says, “lets an unprivileged user ask the driver for GPU write access to memory they can only read”. Stealthium says senior security researcher Branislav Brzak found both bugs and built working exploits, and that “Neither bug needs a special group or capability”.

Nvidia’s bulletin describes CVE-2026-47501 as an out-of-bounds write “by supplying mismatched memory buffers during event buffer setup”, and CVE-2026-47591 as a way to “bypass read-only memory protection due to incorrect authorization”. It scores each 7.8, High, as a local vulnerability.

How long each flaw sat before a fix: Nvidia driver bugs ForgePtr and NvRoot, in the driver since May 2022 per
How long each flaw sat before a fix: Nvidia driver bugs ForgePtr and NvRoot, in the driver since May 2022 per Stealthium and fixed in Nvidia’s 30 September 2026 bulletin; AMD’s Mior, reported in February 2026 per the paper, with BIOS fixes targeted for December 2026 per AMD. The 52 months and month placement are our arithmetic.

Why Rented GPU Servers Are the Exposure

Stealthium’s argument is about shared machines. “MIG partitions the GPU. It does not partition the driver”, it writes. On a node rented out to strangers, it says, local “means every customer on the box”, and it recommends the bugs “be treated as Critical”.

That is the same rented capacity behind this week’s Nvidia numbers: neocloud shares rose after Nvidia said GPU rents went up, and our list-price check found 8-GPU H100 servers at $4.50 to $6.16 an hour. Stealthium also says it has reported “25+ further vulnerabilities across the AI runtime stack”.

Which Drivers Fix It

Nvidia’s bulletin lists four Linux driver branches, with fixed versions 615.71.09, 610.57.04, 595.91.07 and 580.178.04. Its Linux table lists CVE-2026-47501 among the fixes in all three branch rows. Stealthium names 610.57.04, 595.91.07 or 580.178.04 for NvRoot and 615.71.09 for ForgePtr, and says “There is no sysctl or seccomp profile that closes either bug”.

Stealthium’s advice to renters is to ask the provider “which driver version are my workloads running on, and when was it last patched?” The bulletin was first released on 30 September 2026 and updated on 16 November.

A Second Isolation Break: AMD’s SEV-SNP

ETH Zurich researchers published Mior, an attack on AMD’s SEV-SNP confidential computing, in a paper for the ACM CCS ’26 conference. The paper says an attacker with hypervisor privileges, such as a cloud provider, can change the memory view of the chip’s Platform Security Processor, a primitive it calls Device-as-Memory, and that this results in the violation of all the security guarantees SEV-SNP provides.

AMD’s bulletin AMD-SB-3059 assigns CVE-2026-0462, with a CVSS 4.0 score of 5.9. It lists an SEV firmware fix released on 12 August 2026 and BIOS fixes for five EPYC families targeted for December 2026. The paper says the team reported the issue in February 2026, about ten months before that target, by our arithmetic.

The Business Lever

The lever is trust in shared AI hardware. As we read both disclosures, the products sold to tenants are isolation: separate GPU slices, and confidential VMs that keep even the cloud provider out. Both reports say a party on the same machine could get past that isolation until the fixes are installed.

The Structural Read

As we read the two disclosures, the weak point they describe sits below the layers tenants buy: Stealthium says GPU partitions do not partition the driver, and the Mior paper says a hypervisor-level attacker can change what AMD’s security processor sees.

As we read Nvidia’s bulletin, the scoring and the setting differ: Nvidia rates both bugs as local, while Stealthium says that on a node rented to strangers, local means every customer on the box.

Stealthium, Rent a Slice, Get the Host, November 2026

“MIG partitions the GPU. It does not partition the driver”

Three Implications

FOR GPU CLOUD RENTERS Stealthium says renters should ask which driver version their workloads run on and when it was last patched; Nvidia’s fixed Linux versions are 615.71.09, 610.57.04, 595.91.07 and 580.178.04.

FOR CONFIDENTIAL-COMPUTING BUYERS AMD lists an SEV firmware fix from 12 August 2026 and BIOS fixes for five EPYC families targeted for December 2026, and tells customers to contact their OEM for the BIOS update for their product.

FOR THE NEOCLOUD TRADE The bugs sit in the same rented capacity behind this week’s neocloud move; Stealthium says it has reported more than 25 further vulnerabilities across the AI runtime stack.

The Business Engineer Lens

This story maps onto the Business Engineer framework Enterprise AI: From Software to Substrate.

The framework says: “Enterprise SaaS is migrating from ‘tool you buy’ to ‘infrastructure you’re woven into.’”

As we read it, the GPU driver is that kind of woven-in infrastructure: every tenant on a server runs on the same driver, so a flaw there reaches all of them. The framework predates these disclosures and does not discuss GPU drivers or SEV-SNP.

What Is Not Established

Stealthium says the AI runtime attack surface “is being actively exploited in the wild”, but its post does not say that ForgePtr or NvRoot themselves were exploited, and Nvidia’s bulletin does not say so either. We could not establish how many GPU clouds were still running unpatched drivers. The Mior paper describes a research attack; AMD’s bulletin does not report exploitation. We did not contact Nvidia, AMD or the researchers.

This week’s other AI-era security disclosures, Java4Shell and CISA’s patch call, are separate issues.

This Week In The AI Supercycle

AI Lost Its Central Banker, the Lab Oligopoly, and the Future of Open Source

This week’s issue: the Nvidia leadership change, read as the AI build-out losing its central banker: who now finances the GPU landlords, backstops the data centres and sponsors open models, and why two labs are becoming the bank.

Read the full issue →

Business Engineer Framework

Enterprise AI: From Software to Substrate

The Business Engineer framework on software that other systems depend on.

Read the Map of AI →

The Bottom Line

Stealthium says ForgePtr and NvRoot, two bugs in Nvidia’s Linux GPU driver since May 2022, let an unprivileged user on a shared GPU server take over the host; Nvidia fixed them in its September 2026 bulletin and scores both 7.8, the bulletin’s highest score. ETH Zurich’s Mior shows a similar break in AMD’s confidential VMs, with BIOS fixes targeted for December.

97,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.

A note on sourcing. The bug descriptions and quotations are from Stealthium’s post (November 2026) and Nvidia’s September 2026 security bulletin; the Mior details are from ETH Zurich’s ACM CCS ’26 paper and AMD bulletin AMD-SB-3059. The 52-month window and the CVE counts are our arithmetic from those documents. We did not contact Nvidia, AMD or the researchers.

Sources: Stealthium, Rent a Slice, Get the Host: What NvRoot and ForgePtr Say About AI Runtime Trust (Nov 2026) · NVIDIA, Security Bulletin: NVIDIA GPU Display Driver – September 2026 · ETH Zurich, Mior: Breaking AMD SEV-SNP with Device-as-Memory (ACM CCS 26) · AMD, AMD-SB-3059: AMD Secure Encrypted Virtualization (SEV) Vulnerability

Scroll to Top
FourWeekMBA