NVIDIA vGPU Manager (vGPU plugin): MULTI-TENANT ISOLATION: the vGPU Manager grants a guest access to memory the guest

Impact

MULTI-TENANT ISOLATION: the vGPU Manager grants a guest access to memory the guest does not own. That is the core vGPU isolation promise failing - a tenant VM reads memory belonging to the host or to another tenant's vGPU.

Who can reach it

Any unprivileged user inside a guest VM with a vGPU on the affected host.

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