NVIDIA vGPU Manager (vGPU plugin): MULTI-TENANT ISOLATION: the vGPU plugin fails to bound an indexed or pointer-based

Impact

MULTI-TENANT ISOLATION: the vGPU plugin fails to bound an indexed or pointer-based access, and NVIDIA calls out code execution, escalation and information disclosure. This is the guest-to-host escape shape - a tenant VM running code in the hypervisor's vGPU plugin owns every other tenant on that GPU. Affects vGPU 8.x before 8.4, 9.x before 9.4, 10.x before 10.3.

Who can reach it

Any unprivileged user inside a guest VM with a vGPU assigned.

What to do

Upgrade the vGPU Manager on the hypervisor host to the fixed vGPU release. The host component is a kernel module inside the hypervisor, so this is a full node drain: evacuate or power off every tenant VM on the host, upgrade, reboot the host. Guest drivers must be kept within the supported version skew and updated per VM (guest reboot). No VBIOS flash, but expect a maintenance window per host and a matching hypervisor-vendor package (VMware/Citrix/KVM/Nutanix builds ship separately).

References