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

drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure

Two paths through vmw_vkms_init() can leave vmw->crc_workq NULL while
still leaving the rest of the driver in a state that calls
vmw_vkms_cleanup() at module unload:

1. vmw_host_get_guestinfo(GUESTINFO_VBLANK, ...) failing or
returning an oversized buffer -- the common case on hosts
without a VBLANK guestinfo entry -- early-returned before the
workqueue allocation.
2. alloc_ordered_workqueue() returning NULL on memory pressure.

vmw_vkms_cleanup() then calls destroy_workqueue(NULL), which
dereferences wq->name and panics.

Fix the first case by removing the early return: vmw->vkms_enabled
is already false on the rpci-failure path so no work will ever be
queued, and allocating the workqueue unconditionally keeps the
control flow simple. Fix the second case by guarding the cleanup
with a NULL check, since alloc_ordered_workqueue() can still fail
under low memory.
Published: 2026-08-15
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A logic flaw in the VMware graphics driver of the Linux kernel allows the vmw_vkms_init() path to leave an uninitialized workqueue pointer in the vmw structure. During driver cleanup, the empty pointer is passed to destroy_workqueue(), causing the kernel to dereference a NULL pointer and crash. The crash results in a kernel panic, taking the entire system offline. This vulnerability does not provide an attacker with the ability to execute arbitrary code; its main impact is to render the host inoperable. The weakness is a classic NULL pointer dereference (CWE‑476).

Affected Systems

The flaw occurs in the Linux kernel’s vmwgfx driver. Any installation of a Linux kernel that includes the vmwgfx module and lacks the fix from the referenced commit is affected. The kernel version is not explicitly listed in the source, but the commit references the working tree for the current mainline kernel. System owners need to verify whether their kernel build includes the abcde8… patch or a subsequent kernel release that incorporates the change. Users running the kernel without that patch are vulnerable.

Risk and Exploitability

The exploitability of the vulnerability is limited to triggering a driver initialization failure, which can be induced by memory pressure or absence of VBLANK guestinfo on the host. The patch only addresses a crash condition; there is no evidence of remote code execution or privilege escalation. The EPSS score is not available, and the flaw is not listed in the CISA KEV catalog, indicating no publicly documented exploitation. Nonetheless, a local attacker could provoke a kernel panic if they can influence the driver initialization path, resulting in a denial‑of‑service of the host system. Given the lack of remote attack surface and no known exploitation, the risk is moderate, but the impact—a complete system crash—merits immediate attention.

Generated by OpenCVE AI on August 15, 2026 at 13:37 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the vmwgfx workqueueNULL‑check fix (e.g., latest mainline kernel release).
  • If a kernel upgrade is not immediately possible, consider disabling the vmwgfx module to avoid the crash: unload the driver with "modprobe -r vmwgfx" or blacklist it in the boot configuration.
  • Apply the vendor’s patch from the upstream source or wait for the fix to be incorporated into your distribution’s kernel package; refer to the linked kernel git commits for the exact patch.

Generated by OpenCVE AI on August 15, 2026 at 13:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 15 Aug 2026 14:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Sat, 15 Aug 2026 12:45:00 +0000

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

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-15T12:26:50.102Z

Reserved: 2026-08-15T05:44:03.897Z

Link: CVE-2026-74442

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T13:17:48.760

Modified: 2026-08-15T13:17:48.760

Link: CVE-2026-74442

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-15T13:45:03Z

Weaknesses