Service interruption via commands after firmware shutdown
Published Oct 9, 2024 · Updated May 11, 2026
State-management flaw in Linux iwlwifi allows local users to interrupt wireless service through a stopped-firmware code path. The iwlmvm traffic-control work remains active after firmware shutdown, so recalculation reaches scan configuration and sends a host command through an inactive transport. Reachability requires an Intel wireless device using the iwlmvm driver and a stopped firmware state; the documented consequence is a kernel WARNING and loss of availability.
Summary
What happened
State-management flaw in Linux iwlwifi allows local users to interrupt wireless service through a stopped-firmware code path. The iwlmvm traffic-control work remains active after firmware shutdown, so recalculation reaches scan configuration and sends a host command through an inactive transport. Reachability requires an Intel wireless device using the iwlmvm driver and a stopped firmware state; the documented consequence is a kernel WARNING and loss of availability.
The record
- CVE
- CVE-2024-47673
- Published
- Oct 9, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 9, 2024CVE 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=4.18
- Affected versionversion=7d9d0d562b54d2953304693f76bc2bbfbe318c27 <0668ebc8c2282ca1e7eb96092a347baefffb5fe7
- Affected versionversion=7d9d0d562b54d2953304693f76bc2bbfbe318c27 <2c61b561baf92a2860c76c2302a62169e22c21cc
- Affected versionversion=7d9d0d562b54d2953304693f76bc2bbfbe318c27 <55086c97a55d781b04a2667401c75ffde190135c
- Affected versionversion=7d9d0d562b54d2953304693f76bc2bbfbe318c27 <5948a191906b54e10f02f6b7a7670243a39f99f4
- Affected versionversion=7d9d0d562b54d2953304693f76bc2bbfbe318c27 <a15df5f37fa3a8b7a8ec7a339d1e897bc524e28f
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