CVE-2026-80702: drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size
drm/vmwgfx: fix guestmemorydirty bitfield clobbered as size
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.152.1-1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.151 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.103 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.44 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1.8 - Compensating control
In vmwgfx_resource.c, rename the two assignments targeting res->guest_memory_size so they target res->guest_memory_dirty instead: vmw_resource_release() writes 0 (false), and vmw_resource_unbind_list() writes 1 (true).
Event History
Frequently Asked Questions
Which resource lifecycle paths can lead to the corrupted allocation-size state?
The incorrect writes occur in vmw_resource_release(), which stores 0, and vmw_resource_unbind_list(), which stores 1, into guest_memory_size. Later resource revalidation can consume that corrupted value in vmw_bo_dirty_transfer_to_res() and vmw_resource_buf_alloc().
What failures can result once the resource is revalidated?
A zero or one value in the allocation-size field can cause zero-length dirty-page walks or wrap-around ranges. Those ranges can read or write beyond the MOB bitmap, while the intended dirty-state tracking is also not updated.