LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26693: wifi: iwlwifi: mvm: fix a crash when we run out of stations

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix a crash when we run out of stations A DoS tool that injects loads of authentication frames made our AP crash. The iwl_mvm_is_dup() function couldn't find the per-queue dup_data which was not allocated. The root cause for that is that we ran out of stations in the firmware and we didn't really add the station to the firmware, yet we didn't return an error to mac80211. Mac80211 was thinking that we have the station and because of that, sta_info::uploaded was set to 1. This allowed ieee80211_find_sta_by_ifaddr() to return a valid station object, but that ieee80211_sta didn't have any iwl_mvm_sta object initialized and that caused the crash mentioned earlier when we got Rx on that station.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26693 is a Linux kernel Wi-Fi driver denial-of-service issue. A flood of authentication frames can crash an access point using the Intel iwlwifi MVM driver when station tracking is exhausted. This affects availability, not data theft, based on current sources.

Executive priority

Treat as a targeted availability risk for Linux-based Wi-Fi access points. Patch during the next maintenance window, faster for business-critical wireless infrastructure. It is not currently supported as an emergency internet-wide threat by the provided sources.

Technical view

In iwlwifi MVM AP handling, station exhaustion was not reported correctly to mac80211. mac80211 then treated a station as uploaded while iwl_mvm_sta data was uninitialized. Later receive handling could access missing per-queue duplicate-detection data and crash. Kernel stable commits are referenced as fixes.

Likely exposure

Most relevant to Linux systems with Intel iwlwifi MVM hardware operating as Wi-Fi access points or hotspots. Exposure is lower for systems without Intel Wi-Fi, without iwlwifi loaded, or not running AP mode. Exact affected kernel ranges should be verified against vendor kernel advisories.

Exploitation context

The public description cites a DoS tool injecting many authentication frames causing an AP crash. No CISA KEV listing or cited source confirms active exploitation. Practical exploitation appears local wireless-range, not internet-routable, based on the frame-injection scenario.

Researcher notes

No CVSS, CWE, or KEV signal is provided in the source bundle. Affected-version metadata is incomplete and should not be used alone for scoping. Use upstream stable commits and downstream vendor advisories to determine whether a deployed kernel contains the fix.

Mitigation direction

  • Apply Linux distribution kernel updates that include the referenced stable fixes.
  • Prioritize Linux Wi-Fi access points using Intel iwlwifi MVM hardware.
  • If no update is available, monitor vendor guidance for supported backports.
  • Consider reducing reliance on affected AP-mode systems until patched.

Validation and detection

  • Inventory Linux systems using Intel iwlwifi MVM hardware.
  • Identify systems configured for Wi-Fi AP or hotspot mode.
  • Compare running kernels with distribution advisories and linked stable commits.
  • Review kernel logs for iwlwifi or AP crashes under authentication-frame load.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2024-26693 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux57974a55d995468a9a476e24693eb741c649b25f, 57974a55d995468a9a476e24693eb741c649b25f, 57974a55d995468a9a476e24693eb741c649b25funaffected
LinuxLinux6.4, 0, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.