GPU VulnDB

Database/Kernel, userspace & hypervisor

drm/vmwgfx: unvalidated pitch in cursor snooping allows out-of-bounds reads in a VMware guest

CVSS 7.8CVE-2026-99002Kernel, userspace & hypervisorcurated

Impact

vmwgfx copied cursor data from a surface using a pitch supplied by userspace without validating it against the box dimensions, so a local user in a VMware guest can make the kernel read past the surface and leak adjacent kernel memory. The exposure is inside the guest kernel, not the ESXi host: it buys a local user kernel-memory disclosure, not cross-VM escape. This is relevant to operators running Linux VMs on VMware as part of the fleet's management or control-plane tier; bare-metal GPU nodes and VMs on other hypervisors do not load vmwgfx. The fix validates the pitch alongside the box dimensions before copying.

Who can reach it

Local, inside a VMware guest. An unprivileged local user needs access to the vmwgfx DRM device node to drive the cursor path; no authentication beyond a shell on the guest, and no reach from outside the VM.

What to do

Update the guest kernel to one carrying the validation fix (the git.kernel.org stable commits) and reboot the affected VMs. Nothing needs to change on the ESXi host, and no firmware work is involved, so this is ordinary guest kernel patching rather than a hypervisor maintenance window.

References

Related entries

All Kernel, userspace & hypervisor entries

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.