NVIDIA Display Driver CVE-2026-24192

Attacker must already have local, authenticated, low-privileged code execution on a Linux host running an affected NVIDIA Display Driver or Virtual GPU Manager build, with access to the NVIDIA GPU device interfaces (typically the /dev/nvidia* nodes that the driver exposes to user space). No user interaction is required (UI:N) and attack complexity is low (AC:L). Limiting factors: the bug is not remotely reachable (AV:L), so internet-facing exposure alone does not enable exploitation; hosts without the NVIDIA proprietary driver installed (e.g., Nouveau-only systems) or where unprivileged users cannot reach the GPU device nodes are not exploitable; vGPU exploitation requires being a tenant on a hypervisor running Virtual GPU Manager in the affected vGPU 16.x/19.x/20.x lines.

The CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H gives a base score of 7.8 and accurately reflects local, low-complexity, low-privilege exploitation with high impact across confidentiality, integrity, and availability - consistent with a kernel-adjacent driver bug usable for LPE. SSVC corroborates this with Technical Impact: total, while Exploitation: none and Automatable: no indicate it is not currently being weaponized in the wild. EPSS at 0.01% (1st percentile) and the absence of CISA KEV listing align: no public exploit identified at time of analysis. Real-world priority is moderate - patch on any multi-user Linux host, vGPU hypervisor, or shared workstation where untrusted local code can run, but it is not an emergency on single-user desktops. There is no conflict between signals; AV:L is internally consistent with a driver ioctl-style bug.

A low-privileged local user on a Linux workstation, CI runner, ML training node, or vGPU-enabled hypervisor host issues a crafted ioctl or other request to the NVIDIA driver with size/length fields chosen to trigger the numeric type misconversion, overflowing a heap buffer inside driver memory. The attacker then leverages the corrupted kernel-adjacent state to escalate from an unprivileged shell to root, or to read sensitive data from other GPU contexts. No public exploit identified at time of analysis, but the technical impact per SSVC is total.