A local user with GPU access can bypass read-only memory protection because the driver handles CPU and GPU write permissions inconsistently. NVIDIA says successful exploitation might cause privilege escalation, code execution, information disclosure, data tampering, or denial of service.Stealthium demonstrated host-root access on Linux driver 610.43.02, including from an unprivileged GPU-enabled container. This is a controlled research result, not evidence of a campaign. NVIDIA rates the flaw CVSS 3.1 7.8 High; the researcher assesses multi-tenant impact more severely.
What it allows
How Does CVE-2026-47591 Cross the GPU Permission Boundary?
Stealthium says a driver memory-pinning request has separate CPU and GPU permission fields. In affected builds, the driver derives the underlying page permission from the CPU field while granting the GPU write access. That mismatch lets a local user change memory that should remain read-only.
The researchers demonstrated that the altered memory could be used for local privilege escalation. They also found the relevant memory was shared with the host in their GPU-enabled container test. Their result makes shared GPU hosts especially urgent to assess, although it does not establish that every tenant configuration is exploitable.
What Is Known About Exploitation and Priority?
Stealthium reports a working controlled exploit and says it withheld public proof-of-concept details. The CISA KEV catalog snapshot released on 13 November 2026 did not list CVE-2026-47591. Brandefense Blackhole counted two dark-chat posts mentioning this CVE from 18 August through 16 November 2026; the measured unit is posts, not incidents.
Those mentions do not establish active exploitation. We recommend prioritizing shared hosts where untrusted local users or containers can access a GPU device, because Stealthium demonstrated a host boundary crossing in that setting. Use the installed driver branch and tenant access model in your vulnerability prioritization decision. The Vulnerability Intelligence page offers the related product context.
Who is affected
Which CVE-2026-47591 Installations Need Review?
NVIDIA's CVE record covers Linux GeForce, RTX/Quadro/NVS, and Tesla drivers. For R580, versions before 580.178.04 are affected; for R595, before 595.91.07; and for R610, before 610.57.04. The record also lists R615 versions before 615.71.09 for those product families.
The same NVIDIA record lists Virtual GPU Manager on XenServer, VMware vSphere, Red Hat Enterprise Linux KVM, and Ubuntu. It marks vGPU 19 releases through 19.5 and vGPU 20 releases through 20.1 as affected. NVIDIA's fixed Manager releases are 580.178.05 (vGPU 19.6) and 595.91.04 (vGPU 20.2), respectively.
Stealthium says its demonstrated path requires a CUDA-capable NVIDIA GPU and an unprivileged local account with GPU device access. It confirmed the behavior on driver 610.43.02 and rejection on 610.57.04. NVIDIA cautions that its supported-version tables may be incomplete and that earlier branches may also be affected.
Inventory host drivers and Virtual GPU Manager separately, including the actual running version after a restart. Match each installation to its NVIDIA product family and branch before choosing a fix. For older branches without a listed fix, follow NVIDIA's advice to upgrade to the latest supported branch; track the result in your patch management process.
Timeline
- 2026-08-03
Stealthium says NVIDIA shipped fixes for the R610, R595 and R580 Linux driver branches.
- 2026-09-30
NVIDIA first released its GPU Display Driver security bulletin and the CVE record was published.
- 2026-10-13
NVIDIA updated its bulletin to version 2.0.0; its stated revision corrected the score of a different CVE.
- 2026-11-16
By this review date, Stealthium's public research described its controlled host-root test and defensive detection ideas.
What to do
-
Identify GPU-enabled hosts and tenants
Record Linux driver or Virtual GPU Manager versions and whether untrusted users or containers can access GPU devices. Prioritize shared hosts where Stealthium demonstrated host-level impact.
-
Apply the NVIDIA branch fix
For covered Linux drivers, install R580 580.178.04, R595 595.91.07, R610 610.57.04, or R615 615.71.09 or a later fixed build on that branch. For Virtual GPU Manager, use 19.6 (580.178.05) or 20.2 (595.91.04), as applicable.
-
Verify the running version
After the update and any required host restart, inspect the active NVIDIA driver or Manager release on each host. Confirm it meets the listed fixed version for its product and branch; do not rely only on an installed package record.
-
Restrict access until fixed and review telemetry
Stealthium advises withholding GPU device access from untrusted tenants on unpatched hosts. If available, review driver-level telemetry for contradictory CPU and GPU permissions and unexpected GPU writes to protected file-backed memory; preserve findings for investigation.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-47591 in Brandefense Atlas
The Atlas record of CVE-2026-47591: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can NvRoot cross from a container to its GPU host?
Stealthium demonstrated host-root access from an unprivileged container with GPU access on driver 610.43.02. That test establishes a possible host boundary crossing in the tested configuration, not universal exposure across all container setups.
Which NVIDIA driver releases fix CVE-2026-47591?
NVIDIA lists Linux driver fixes at R580 580.178.04, R595 595.91.07, R610 610.57.04, and R615 615.71.09. Its Virtual GPU Manager fixes are vGPU 19.6 and 20.2. Verify the active host release after updating.
Is NVIDIA's 7.8 score the same as Stealthium's 9.3 assessment?
No. NVIDIA assigns CVSS 3.1 7.8 High. Stealthium separately estimates CVSS 4.0 9.3 Critical for the multi-tenant scenario; the two scores use different versions and assessment scopes.