{"api_version":"1","generated_at":"2026-08-15T15:13:41+00:00","cve":"CVE-2026-74442","urls":{"html":"https://cve.report/CVE-2026-74442","api":"https://cve.report/api/cve/CVE-2026-74442.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74442","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74442"},"summary":{"title":"drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 13:17:48","updated_at":"2026-08-15 13:17:48"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/05eaa887e7b4f40fba425f8a1d7a5a8a043092a6","name":"https://git.kernel.org/stable/c/05eaa887e7b4f40fba425f8a1d7a5a8a043092a6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0ee0532f1d405d37f38c44cbba87342e63d3bbd4","name":"https://git.kernel.org/stable/c/0ee0532f1d405d37f38c44cbba87342e63d3bbd4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/96efee36453b697ccbaf75091b7a1807c11809dd","name":"https://git.kernel.org/stable/c/96efee36453b697ccbaf75091b7a1807c11809dd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7c701778c6a369769992614dac8dc00c8ac72afc","name":"https://git.kernel.org/stable/c/7c701778c6a369769992614dac8dc00c8ac72afc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74442","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74442","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 7c701778c6a369769992614dac8dc00c8ac72afc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 96efee36453b697ccbaf75091b7a1807c11809dd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 0ee0532f1d405d37f38c44cbba87342e63d3bbd4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 05eaa887e7b4f40fba425f8a1d7a5a8a043092a6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.103 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.44 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.8 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc6 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"7c701778c6a369769992614dac8dc00c8ac72afc","status":"affected","version":"7b0062036c3b71b4a69e244ecf0502c06c4cf5f0","versionType":"git"},{"lessThan":"96efee36453b697ccbaf75091b7a1807c11809dd","status":"affected","version":"7b0062036c3b71b4a69e244ecf0502c06c4cf5f0","versionType":"git"},{"lessThan":"0ee0532f1d405d37f38c44cbba87342e63d3bbd4","status":"affected","version":"7b0062036c3b71b4a69e244ecf0502c06c4cf5f0","versionType":"git"},{"lessThan":"05eaa887e7b4f40fba425f8a1d7a5a8a043092a6","status":"affected","version":"7b0062036c3b71b4a69e244ecf0502c06c4cf5f0","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.10"},{"lessThan":"6.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.103","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.44","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.8","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc6","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.103","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.44","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc6","versionStartIncluding":"6.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"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."}],"providerMetadata":{"dateUpdated":"2026-08-15T12:26:50.102Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/7c701778c6a369769992614dac8dc00c8ac72afc"},{"url":"https://git.kernel.org/stable/c/96efee36453b697ccbaf75091b7a1807c11809dd"},{"url":"https://git.kernel.org/stable/c/0ee0532f1d405d37f38c44cbba87342e63d3bbd4"},{"url":"https://git.kernel.org/stable/c/05eaa887e7b4f40fba425f8a1d7a5a8a043092a6"}],"title":"drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74442","datePublished":"2026-08-15T12:26:50.102Z","dateReserved":"2026-08-15T05:44:03.897Z","dateUpdated":"2026-08-15T12:26:50.102Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 13:17:48","lastModifiedDate":"2026-08-15 13:17:48","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74442","Ordinal":"1","Title":"drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure","CVE":"CVE-2026-74442","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74442","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure"}]}}}