NVIDIA vGPU Manager (vGPU plugin + host kernel module): MULTI-TENANT ISOLATION: the host can be made to write outside

Impact

MULTI-TENANT ISOLATION: the host can be made to write outside the frame-buffer region allocated to a guest. That is a direct breach of the vGPU frame-buffer partition - one tenant's writes landing in memory belonging to the host or another tenant's vGPU. vGPU 8.x before 8.5, 10.x before 10.4, and 11.0.

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