CVE-2026-74442

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure<br /> <br /> Two paths through vmw_vkms_init() can leave vmw-&gt;crc_workq NULL while<br /> still leaving the rest of the driver in a state that calls<br /> vmw_vkms_cleanup() at module unload:<br /> <br /> 1. vmw_host_get_guestinfo(GUESTINFO_VBLANK, ...) failing or<br /> returning an oversized buffer -- the common case on hosts<br /> without a VBLANK guestinfo entry -- early-returned before the<br /> workqueue allocation.<br /> 2. alloc_ordered_workqueue() returning NULL on memory pressure.<br /> <br /> vmw_vkms_cleanup() then calls destroy_workqueue(NULL), which<br /> dereferences wq-&gt;name and panics.<br /> <br /> Fix the first case by removing the early return: vmw-&gt;vkms_enabled<br /> is already false on the rpci-failure path so no work will ever be<br /> queued, and allocating the workqueue unconditionally keeps the<br /> control flow simple. Fix the second case by guarding the cleanup<br /> with a NULL check, since alloc_ordered_workqueue() can still fail<br /> under low memory.