NVIDIA GPU driver for Windows: missing authorization in the kernel module allows cross-scope information disclosure
Impact
A local user on a Windows GPU node can reach a kernel module path that fails to check authorization, yielding information disclosure and data tampering. The CVSS vector has a changed scope (S:C) with high confidentiality impact, which means the data obtained is outside the attacker's own security boundary - on a shared Windows GPU host that can mean another session's data. Relevant to operators running Tesla-class cards under Windows Server for rendering or inference; Linux fleets are unaffected by this id.
Who can reach it
Local authenticated user with low privileges on a Windows host that has the NVIDIA display driver loaded.
What to do
Update the Windows GPU display driver to the fixed branch listed in NVIDIA bulletin 2026/5861. A driver update on Windows requires a reboot, so plan a node drain and reboot per host.
References
Related entries
- LACT: polkit authorization keyed on peer PID lets a local user bypass authentication to the GPU control daemonCVE-2026-75037 · LACT (Linux AMDGPU Controller Tool) privileged daemon - polkit UnixProcessSubject/peer-PID authenticationHigh
- DGX servers BMC: OS command injection on BMCCVE-2022-42279 · DGX servers BMCHigh
- DGX-2 SBIOS: OS command injection in firmwareCVE-2022-42289 · DGX-2 SBIOSHigh
- DGX-2 SBIOS: OS command injection in BIOSCVE-2022-42290 · DGX-2 SBIOSHigh
- BlueField-2 / BlueField-3 DPU BMC: Code injection on DPU BMCCVE-2023-31037 · BlueField-2 / BlueField-3 DPU BMCHigh
- NVIDIA Windows GPU Display Driver (nvlddmkm.sys): A kernel object created by the escape handler gets defaultCVE-2019-5687 · NVIDIA Windows GPU Display Driver (nvlddmkm.sys)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.