Kernel crash via unchecked workqueue allocation
Published Aug 19, 2025 · Updated May 11, 2026
Unchecked return value in the Linux iwlwifi DVM driver allows local users to crash the kernel after a workqueue allocation failure. drivers/net/wireless/intel/iwlwifi/dvm/main.c stores the alloc_ordered_workqueue() result without checking whether it is NULL before later workqueue use. Reachability requires the iwlwifi DVM driver and a failed ordered-workqueue allocation; the documented consequence is availability loss only.
Summary
What happened
Unchecked return value in the Linux iwlwifi DVM driver allows local users to crash the kernel after a workqueue allocation failure. drivers/net/wireless/intel/iwlwifi/dvm/main.c stores the alloc_ordered_workqueue() result without checking whether it is NULL before later workqueue use. Reachability requires the iwlwifi DVM driver and a failed ordered-workqueue allocation; the documented consequence is availability loss only.
The record
- CVE
- CVE-2025-38602
- Published
- Aug 19, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-252, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.24
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <2e9f85ee3b46453a2f250a57d3a9f10c70c71202
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <6663c52608d8d8727bf1911e6d9218069ba1c85e
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <70a1b527eaea9430b1bd87de59f3b9f6bd225701
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <7dd6350307af6521b6240b295c93b7eec4daebe6
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <90a0d9f339960448a3acc1437a46730f975efd6a
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <b398120fbe0acfef60b16f6a0f69902d385d7728
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <c0e43c3f6c0a79381b468574c241065998412b7c
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <c80832d445653baba5ac80cd2c2637c437ac881b
- Affected versionversion=b481de9ca074528fe8c429604e2777db8b89806a <ca980f1911a7144d451d1c31298ab8507c6bd88f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo