NVIDIA GPU driver: improper access control in the kernel mode layer allows local denial of service

CVSS 5.5CVE-2026-47492NVIDIA / GPU stackcurated

Impact

An unprivileged local user can reach a kernel mode layer path that does not enforce access control properly and knock out GPU availability. Confidentiality and integrity impact are none; this is availability only. On a shared GPU node that is still real: any tenant with a GPU pod can take the device away from the other tenants on that node, and recovering a wedged GPU driver generally means a reboot and losing the running jobs. The guest driver and Virtual GPU Manager are both in the affected list.

Who can reach it

Any local low-privileged user with access to the GPU device nodes - a tenant container is enough. No privileged role needed.

What to do

Update the GPU display driver, guest driver and vGPU manager to the fixed branches in NVIDIA bulletin 2026/5861. Drain the node and reboot to reload the kernel modules.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-47492 https://github.com/NVIDIA/product-security/tree/main/2026/5861 https://www.cve.org/CVERecord?id=CVE-2026-47492

Related entries

All NVIDIA / GPU stack entries

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.