https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 23:47:47 +0000 https://vulnerability.circl.lu/vuln/cve-2026-80702 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size</p> <p>Two sites in vmwgfx_resource.c assign boolean literals to res-&gt;guest_memory_size, which is an unsigned long allocation-size field; the intended target is the adjacent res-&gt;guest_memory_dirty bitfield. After the assignments the field holds 0 or 1 instead of the resource&#39;s MOB allocation size:</p> <p>- vmw_resource_release() writes 0 (false), and - vmw_resource_unbind_list() writes 1 (true).</p> <p>Subsequent revalidation paths read guest_memory_size when computing the dirty page range (vmw_bo_dirty_transfer_to_res()) and the buffer allocation size (vmw_resource_buf_alloc()), producing zero-length walks or wrap-around ranges that read or write past the MOB bitmap. The dirty-tracking intent of the original code (mark the resource as dirtied since the last sync) is also lost, since guest_memory_dirty is never updated.</p> <p>Rename both assignments to guest_memory_dirty.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size</p> <p>Two sites in vmwgfx_resource.c assign boolean literals to res-&gt;guest_memory_size, which is an unsigned long allocation-size field; the intended target is the adjacent res-&gt;guest_memory_dirty bitfield. After the assignments the field holds 0 or 1 instead of the resource&#39;s MOB allocation size:</p> <p>- vmw_resource_release() writes 0 (false), and - vmw_resource_unbind_list() writes 1 (true).</p> <p>Subsequent revalidation paths read guest_memory_size when computing the dirty page range (vmw_bo_dirty_transfer_to_res()) and the buffer allocation size (vmw_resource_buf_alloc()), producing zero-length walks or wrap-around ranges that read or write past the MOB bitmap. The dirty-tracking intent of the original code (mark the resource as dirtied since the last sync) is also lost, since guest_memory_dirty is never updated.</p> <p>Rename both assignments to guest_memory_dirty.</p> https://vulnerability.circl.lu/vuln/cve-2026-80702