CVE-2024-35937: wifi: cfg80211: check A-MSDU format more carefully
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: check A-MSDU format more carefully
If it looks like there's another subframe in the A-MSDU
but the header isn't fully there, we can end up reading
data out of bounds, only to discard later. Make this a
bit more careful and check if the subframe header can
even be present.
Security readout for executives and security teams
Plain-English summary
A malformed Wi-Fi A-MSDU frame can make an affected Linux kernel read beyond the available packet data. A nearby, unauthenticated transmitter may be able to trigger confidentiality loss or system disruption without user interaction. The supplied CVSS score is 8.1, making this a high-priority issue for Linux devices with active wireless interfaces.
Executive priority
Treat this as a high-priority patching item for wireless-enabled Linux fleets, especially mobile endpoints and exposed appliances. It does not warrant an emergency response based solely on current evidence because active exploitation is not established, but adjacent, unauthenticated triggering and possible confidentiality or availability impact justify prompt remediation.
Technical view
The flaw is an out-of-bounds read in Linux cfg80211 A-MSDU parsing. Code could infer another subframe existed without first confirming that its complete header was present. The stable-kernel changes add stricter length validation before processing the subframe. The supplied CVSS vector requires adjacent-network access and indicates potentially high confidentiality and availability impact.
Likely exposure
Exposure is most likely on Linux endpoints, appliances, and embedded systems using Wi-Fi with a vulnerable kernel. The supplied affected-version data is ambiguous and includes versions and commit identifiers with conflicting default statuses, so distribution package and backport status must be verified rather than inferred from version numbers alone.
Exploitation context
CISA KEV status is false, and the supplied sources do not establish active exploitation or a public working exploit. Exploitation would require adjacent-network reachability, consistent with a nearby malicious wireless transmitter. No privileges or user interaction are indicated by the supplied CVSS vector.
Researcher notes
The core condition is incomplete A-MSDU subframe-header validation leading to an out-of-bounds read before later rejection. Assessments should account for distribution backports and runtime wireless capability. The bundle does not identify the exact leaked data, crash behavior, practical exploit reliability, or affected driver combinations; those points require vendor-specific confirmation.
Mitigation direction
Install the vendor-supported kernel update containing the applicable stable fix, then reboot into it.
Check distribution security guidance because vendors may backport fixes without changing to an obvious upstream version.
Prioritize wireless-enabled systems in public, shared, or otherwise untrusted radio environments.
Where updating is delayed, disable unnecessary Wi-Fi interfaces and use trusted wired connectivity when operationally feasible.
Validation and detection
Inventory running kernel and distribution package versions on every wireless-enabled Linux system.
Confirm the installed package includes the relevant upstream fix or documented vendor backport.
Verify systems rebooted into the updated kernel rather than retaining the vulnerable kernel in memory.
Identify whether cfg80211 and wireless interfaces are present, enabled, and operational.
Re-run authenticated vulnerability checks after updating and review vendor advisory mappings.
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-35937 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.