NVIDIA vGPU guest graphics driver: Bad cleanup on a failure path in the guest driver crashes the tenant's own VM
Impact
Bad cleanup on a failure path in the guest driver crashes the tenant's own VM. Self-inflicted blast radius only, but it is a reliable way for a tenant to lose their own workload and blame the platform.
Who can reach it
A user inside the guest VM (or any workload that triggers the failure path).
What to do
Upgrade the vGPU Manager on the host and the vGPU guest driver inside each tenant VM to the fixed release. Host side is a node drain plus reboot; guest side is a per-VM driver install and reboot. Because the guest driver is inside tenant-controlled VMs, in a multi-tenant estate you cannot fully remediate the guest half yourself - the host-side upgrade is the control you own. No VBIOS flash.
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.