Answer in brief
CVE-2025-38045 records a Medium severity (CVSS 5.5) vulnerability in wifi: iwlwifi: fix debug actions order. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f21baf244112e646c6b6c9db94834cf06358db06 <49d7587274282fd92a7db6b70dfbc7c973f4f52b || >=f21baf244112e646c6b6c9db94834cf06358db06 <2b790fe67ed483d86c1aeb8be6735bf792caa7e5 || >=f21baf244112e646c6b6c9db94834cf06358db06 <181e8b56b74ad3920456dcdc8a361520d9007956 || >=f21baf244112e646c6b6c9db94834cf06358db06 <328fbc96ecbee16c5fcbfcb3ac57b476f94da2f0 || >=f21baf244112e646c6b6c9db94834cf06358db06 <eb29b4ffafb20281624dcd2cbb768d6f30edf600 | 49d7587274282fd92a7db6b70dfbc7c973f4f52b, 2b790fe67ed483d86c1aeb8be6735bf792caa7e5, 181e8b56b74ad3920456dcdc8a361520d9007956, 328fbc96ecbee16c5fcbfcb3ac57b476f94da2f0, eb29b4ffafb20281624dcd2cbb768d6f30edf600 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 30, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: fix debug actions order The order of actions taken for debug was implemented incorrectly. Now we implemented the dump split and do the FW reset only in the middle of the dump (rather than the FW killing itself on error.) As a result, some of the actions taken when applying the config will now crash the device, so we need to fix the order.
Quoted source text, attributed separately from HOL analysis.