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

Related entries

• NVIDIA Windows GPU Display Driver, DirectX 11 user-mode driver (nvwgf2um.dll): A crafted shader causes an out-of-boundsCVE-2020-5965 · NVIDIA Windows GPU Display Driver, DirectX 11 user-mode driver (nvwgf2um.dll)Medium
• NVIDIA vGPU Manager (vGPU plugin): Guest-supplied size not validated in the vGPU pluginCVE-2020-5986 · NVIDIA vGPU Manager (vGPU plugin)Medium
• NVIDIA vGPU Manager (vGPU plugin): NULL dereference in the vGPU plugin reachable from a guest - one tenant crashes theCVE-2020-5989 · NVIDIA vGPU Manager (vGPU plugin)Medium
• NVIDIA GPU Display Driver (Windows nvlddmkm.sys + Linux nvidia.ko): Improper validation of a user-supplied pointerCVE-2021-1053 · NVIDIA GPU Display Driver (Windows nvlddmkm.sys + Linux nvidia.ko)Medium
• NVIDIA Windows GPU Display Driver (nvlddmkm.sys): Missing authorization check in the escape handlerCVE-2021-1054 · NVIDIA Windows GPU Display Driver (nvlddmkm.sys)Medium
• NVIDIA vGPU Manager (vGPU plugin): Unvalidated guest input causes unbounded resource consumption on the host, so oneCVE-2021-1066 · NVIDIA vGPU Manager (vGPU plugin)Medium