CVE-2026-74442

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.

CVSS

No CVSS.

References

Link	Resource
https://git.kernel.org/stable/c/05eaa887e7b4f40fba425f8a1d7a5a8a043092a6
https://git.kernel.org/stable/c/0ee0532f1d405d37f38c44cbba87342e63d3bbd4
https://git.kernel.org/stable/c/7c701778c6a369769992614dac8dc00c8ac72afc
https://git.kernel.org/stable/c/96efee36453b697ccbaf75091b7a1807c11809dd

Configurations

No configuration.

History

No history.

Information

Published : 2026-08-15 13:17

Updated : 2026-08-17 06:19

NVD link : CVE-2026-74442

Mitre link : CVE-2026-74442

CVE.ORG link : CVE-2026-74442

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-74442", "cveTags": [], "metrics": {}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "7b0062036c3b71b4a69e244ecf0502c06c4cf5f0", "lessThan": "7c701778c6a369769992614dac8dc00c8ac72afc", "versionType": "git"}, {"status": "affected", "version": "7b0062036c3b71b4a69e244ecf0502c06c4cf5f0", "lessThan": "96efee36453b697ccbaf75091b7a1807c11809dd", "versionType": "git"}, {"status": "affected", "version": "7b0062036c3b71b4a69e244ecf0502c06c4cf5f0", "lessThan": "0ee0532f1d405d37f38c44cbba87342e63d3bbd4", "versionType": "git"}, {"status": "affected", "version": "7b0062036c3b71b4a69e244ecf0502c06c4cf5f0", "lessThan": "05eaa887e7b4f40fba425f8a1d7a5a8a043092a6", "versionType": "git"}], "programFiles": ["drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.10"}, {"status": "unaffected", "version": "0", "lessThan": "6.10", "versionType": "semver"}, {"status": "unaffected", "version": "6.12.103", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.44", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.1.8", "versionType": "semver", "lessThanOrEqual": "7.1.*"}, {"status": "unaffected", "version": "7.2", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c"], "defaultStatus": "affected"}]}], "published": "2026-08-15T13:17:48.760", "references": [{"url": "https://git.kernel.org/stable/c/05eaa887e7b4f40fba425f8a1d7a5a8a043092a6", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/0ee0532f1d405d37f38c44cbba87342e63d3bbd4", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/7c701778c6a369769992614dac8dc00c8ac72afc", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/96efee36453b697ccbaf75091b7a1807c11809dd", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Received", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure\n\nTwo paths through vmw_vkms_init() can leave vmw->crc_workq NULL while\nstill leaving the rest of the driver in a state that calls\nvmw_vkms_cleanup() at module unload:\n\n 1. vmw_host_get_guestinfo(GUESTINFO_VBLANK, ...) failing or\n returning an oversized buffer -- the common case on hosts\n without a VBLANK guestinfo entry -- early-returned before the\n workqueue allocation.\n 2. alloc_ordered_workqueue() returning NULL on memory pressure.\n\nvmw_vkms_cleanup() then calls destroy_workqueue(NULL), which\ndereferences wq->name and panics.\n\nFix the first case by removing the early return: vmw->vkms_enabled\nis already false on the rpci-failure path so no work will ever be\nqueued, and allocating the workqueue unconditionally keeps the\ncontrol flow simple. Fix the second case by guarding the cleanup\nwith a NULL check, since alloc_ordered_workqueue() can still fail\nunder low memory."}], "lastModified": "2026-08-17T06:19:39.970", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}