NVIDIA vGPU Virtual GPU Manager: incorrect numeric conversion in the kernel mode layer

Impact

An incorrect numeric conversion in the host vGPU manager's kernel mode layer lets a privileged local caller drive the driver out of bounds, with code execution, privilege escalation, information disclosure, data tampering and denial of service listed. This is host-side code on a vGPU hypervisor, so a crash takes down every guest sharing the physical GPU, not one tenant. High privileges on the host are required, which puts it in the depth-in-depth category rather than the guest-escape category - unlike CVE-2026-47496 in the same bulletin.

Who can reach it

Local attacker with high privileges on the vGPU host (not inside a guest).

What to do

Update the vGPU Virtual GPU Manager to the fixed branch in NVIDIA bulletin 2026/5861. Evacuate the vGPU guests, drain the host and reboot to replace the kernel modules.

References

Related entries

• NVIDIA vGPU Virtual GPU Manager: out-of-bounds read in the kernel mode layerCVE-2026-47544 · NVIDIA vGPU Virtual GPU Manager for Linux (kernel mode layer out-of-bounds read)Medium
• NVIDIA GPU firmware: improper input validation reachable from a privileged local userCVE-2026-47546 · NVIDIA GPU firmware (input validation)Medium
• NVIDIA GPU Display Driver (Windows nvlddmkm.sys + Linux nvidia.ko): Improper access control in the kernel-mode layerCVE-2021-1076 · NVIDIA GPU Display Driver (Windows nvlddmkm.sys + Linux nvidia.ko)Medium
• NVIDIA GPU Display Driver (Windows nvlddmkm.sys + Linux nvidia.ko): Reference-count mishandling on a driver resourceCVE-2021-1077 · NVIDIA GPU Display Driver (Windows nvlddmkm.sys + Linux nvidia.ko)Medium
• GPU Display Driver: Local privesc (kernel buffer overflow)CVE-2023-0198 · GPU Display DriverMedium
• DGX H100 BMC (REST): Privesc via auth flawCVE-2023-31015 · DGX H100 BMC (REST)Medium