NVIDIA vGPU Manager (vGPU plugin): MULTI-TENANT ISOLATION: double free in the vGPU Manager that NVIDIA explicitly
Impact
MULTI-TENANT ISOLATION: double free in the vGPU Manager that NVIDIA explicitly describes as a write-what-where condition allowing arbitrary code execution. A tenant VM writing chosen values to chosen host addresses is a full hypervisor-host compromise from inside a guest.
Who can reach it
Any unprivileged user inside a guest VM with a vGPU.
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
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.