CVE-2025-21930: wifi: iwlwifi: mvm: don't try to talk to a dead firmware
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: don't try to talk to a dead firmware
This fixes:
bad state = 0
WARNING: CPU: 10 PID: 702 at drivers/net/wireless/inel/iwlwifi/iwl-trans.c:178 iwl_trans_send_cmd+0xba/0xe0 [iwlwifi]
Call Trace:
<TASK>
? __warn+0xca/0x1c0
? iwl_trans_send_cmd+0xba/0xe0 [iwlwifi 64fa9ad799a0e0d2ba53d4af93a53ad9a531f8d4]
iwl_fw_dbg_clear_monitor_buf+0xd7/0x110 [iwlwifi 64fa9ad799a0e0d2ba53d4af93a53ad9a531f8d4]
_iwl_dbgfs_fw_dbg_clear_write+0xe2/0x120 [iwlmvm 0e8adb18cea92d2c341766bcc10b18699290068a]
Ask whether the firmware is alive before sending a command.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21930 is a Linux kernel wireless driver flaw in iwlwifi. The driver may try to communicate with firmware that is no longer alive, causing a kernel warning and potential availability impact. It is local-only and does not indicate data theft or privilege escalation in the supplied sources.
Executive priority
Treat as a routine but real availability risk for Linux endpoints with Intel Wi-Fi. It does not justify emergency response based on the supplied evidence, but it should be included in normal kernel patch cycles and endpoint reliability remediation.
Technical view
The issue is in Linux iwlwifi mvm debug handling. A firmware debug clear path can reach iwl_trans_send_cmd after firmware death, triggering a bad-state warning. The fix checks whether firmware is alive before sending the command. CVSS is 5.5: local, low complexity, low privilege, no confidentiality or integrity impact, high availability impact.
Likely exposure
Exposure is most likely on Linux systems using Intel iwlwifi wireless hardware and affected kernel versions or unpatched downstream builds. Servers without this driver or wireless stack are less likely exposed. Distro backports may change apparent version status, so validate by vendor kernel package and patch level.
Exploitation context
The source bundle does not show KEV listing or active exploitation. The CVSS vector indicates local access with low privileges and no user interaction. Impact is availability, not confidentiality or integrity. Evidence is limited to kernel advisory text and stable patch references.
Researcher notes
The public description identifies a defensive state check in iwlwifi mvm debugfs-related handling. The affected-version data is not fully self-explanatory, and downstream distro status requires vendor confirmation. No exploit path, public weaponization, or broad remote attack surface is established in the provided sources.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check distribution advisories for backported iwlwifi fixes.
Prioritize Linux laptops and wireless-enabled endpoints using Intel Wi-Fi.
If patching is delayed, monitor for kernel warnings or driver instability.
Avoid assuming upstream version numbers match distro package security status.
Validation and detection
Inventory Linux hosts with Intel iwlwifi or iwlmvm loaded.
Map kernel packages against vendor advisories and fixed stable commits.
Review kernel logs for iwlwifi bad-state warnings.
Confirm patched builds include the firmware-alive check before command send.
Document any exposed systems awaiting vendor-fixed kernels.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21930 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.