NVIDIA GPU Driver CVE-2026-47599

Requires an unprivileged local user account (PR:L, AV:L) on a Linux system running the NVIDIA open-source GPU kernel module; exploitation works against default configurations of that module but is limited to the open-source kernel module variant (not the proprietary module) and demands a triggerable DMA mapping code path. No user interaction is needed (UI:N). Limiting factors: attacker must already have local execution on the host and the affected open-source kernel module must be installed and loaded, making this most relevant to multi-user, VDI, cloud-GPU, and HPC deployments rather than remote attack surface.

All exploitation signals point to a local privilege-escalation risk rather than a remote-critical one. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8 HIGH) requires local access and low privileges - an unprivileged local user account already on the Linux host. There is no EPSS score, no CISA KEV listing, and no public POC provided, so this is 'no public exploit identified at time of analysis.' No SSVC decision data is supplied. The 'RCE' tag overstates reach: with AV:L this is local code execution within the kernel context, not remote code execution - treat the tag as loose. The described impact (code execution, privilege escalation, DoS, information disclosure, data tampering) is broad but gated behind local access; NVIDIA self-reported and patched via bulletin 5861, consistent with a defense-in-depth kernel fix. Net: a genuine but not emergency issue - meaningful on shared/multi-tenant Linux GPU hosts (VDI, cloud GPU, HPC), lower urgency on single-user workstations.

An unprivileged local user on a Linux system running the NVIDIA open-source kernel module triggers a DMA mapping operation that improperly preserves memory access permissions, gaining write or access rights the mapping should not grant. By leveraging the retained permissions against kernel-owned or cross-context memory, the attacker escalates to kernel-level code execution or leaks sensitive data. No public exploit code is currently identified, and exploitation requires an existing local account on the target.