NVIDIA vGPU Manager kernel module (nvidia.ko, host): One vGPU can starve the other vGPUs hosted on the same physical

Impact

One vGPU can starve the other vGPUs hosted on the same physical GPU of resources. This is the noisy-neighbour problem as a security bug: a tenant deliberately degrades every co-tenant on the card, and nothing in the vGPU scheduler stops them.

Who can reach it

Any user inside a guest VM sharing a physical GPU with other tenants.

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