NVIDIA vGPU Manager (vGPU plugin): A guest can deadlock the vGPU plugin. A hung plugin does not crash-and-restart

Impact

A guest can deadlock the vGPU plugin. A hung plugin does not crash-and-restart cleanly - it wedges the GPU for every tenant on it until the host is reset.

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

Related entries

• NVIDIA vGPU Manager (vGPU plugin): An index value from the guest is not validated by the vGPU plugin, letting oneCVE-2019-5698 · NVIDIA vGPU Manager (vGPU plugin)Medium
• NVIDIA vGPU Manager (vGPU plugin): Another guest-reachable NULL dereference in the vGPU plugin causing denial ofCVE-2021-1103 · NVIDIA vGPU Manager (vGPU plugin)Medium
• NVIDIA vGPU Manager (vGPU plugin): The vGPU plugin fails to bound an indexed or pointer-based access, and NVIDIA callsCVE-2020-5968 · NVIDIA vGPU Manager (vGPU plugin)High
• NVIDIA vGPU Manager (vGPU plugin): Out-of-bounds read in the vGPU plugin that NVIDIA rates as code-execution capable. ACVE-2020-5971 · NVIDIA vGPU Manager (vGPU plugin)High
• NVIDIA vGPU Manager (vGPU plugin): Use-after-free while releasing resources in the vGPU plugin, rated code-executionCVE-2020-5984 · NVIDIA vGPU Manager (vGPU plugin)High
• NVIDIA vGPU Manager (vGPU plugin): Parameters stay writable by the guest after the plugin has validated them - aCVE-2020-5987 · NVIDIA vGPU Manager (vGPU plugin)High