AZL-98051

In the Linux kernel, the following vulnerability has been resolved:

drm/vmwgfx: fix guestmemorydirty bitfield clobbered as size

Two sites in vmwgfxresource.c assign boolean literals to res->guestmemorysize, which is an unsigned long allocation-size field; the intended target is the adjacent res->guestmemory_dirty bitfield. After the assignments the field holds 0 or 1 instead of the resource's MOB allocation size:

• vmwresourcerelease() writes 0 (false), and
• vmwresourceunbind_list() writes 1 (true).

Subsequent revalidation paths read guestmemorysize when computing the dirty page range (vmwbodirtytransfertores()) and the buffer allocation size (vmwresourcebufalloc()), 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 guestmemorydirty is never updated.

Rename both assignments to guestmemorydirty.