CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's vmwgfx driver, where boolean literals are incorrectly assigned to the `guest_memory_size` field instead of the intended `guest_memory_dirty` bitfield. This misassignment can lead to improper handling of memory allocation sizes, resulting in potential out-of-bounds memory access and loss of dirty tracking for resources. Organizations utilizing Linux systems with the vmwgfx driver should prioritize this issue to mitigate risks associated with memory corruption and data integrity.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size Two sites in vmwgfx_resource.c assign boolean literals to res->guest_memory_size, which is an unsigned long allocation-size field; the intended target is the adjacent res->guest_memory_dirty bitfield. After the assignments the field holds 0 or 1 instead of the resource's MOB allocation size: - vmw_resource_release() writes 0 (false), and - vmw_resource_unbind_list() writes 1 (true). 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. Rename both assignments to guest_memory_dirty.