CVE-2026-93805wifi: cfg80211: validate rx/tx MLME callback frame lengths before access
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: validate rx/tx MLME callback frame lengths before access cfg80211_rx_mlme_mgmt() and cfg80211_tx_mlme_mgmt() call tracepoints before rejecting frames shorter than the frame-control field. After that, they only require len >= 2 before dispatching into subtype handlers that assume their fixed fields are present. The frames that trip this are not shorter than 2 bytes; they are short relative to their subtype. mwifiex is a concrete in-tree example on the length side: mwifiex_process_mgmt_packet() only requires a 4-address ieee80211_hdr plus the 2-byte firmware length prefix before handing the frame to cfg80211_rx_mlme_mgmt(). After stripping the length prefix and removing addr4, pkt_len can be exactly 24: a bare 3-address management header with no reason-code body. The existing WARN_ON(len < 2) does not fire on such a frame, and cfg80211_process_deauth() then reads u.deauth.reason_code as a two-byte access starting at offset 24, immediately past the 24-byte buffer. Add a frame-control length gate, then validate each subtype's minimum frame size in an if/else-if chain that mirrors the dispatch logic. Trace only after the frame is known to be well-formed. Side effects of this change: - The WARN_ON(len < 2) is dropped. It only guarded the frame_control read, never the subtype fixed fields, and it does not fire on the frames that actually trigger the out-of-bounds read (which are >= 2). The len >= 2 check is kept as the guard before dereferencing frame_control, but without the warning: these are exported callbacks and a malformed frame from a driver should be dropped silently rather than backtraced. - cfg80211_tx_mlme_mgmt() previously routed every non-deauth subtype through disassociation handling; it now silently ignores unrecognised subtypes.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 9 days later
· 9 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 – < 6eb4bd50be53f5afbabb3a3b5153276e08fa7a4a
- affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 – < ce2a3be6909462f49c34de96be71f0ad5f0d573f
- affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 – < 6bdf4dcff98df634e04ebf99f52027a48d7f78ff
- affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 – < 0ec738a0d361d7eb37188117166d201f9df622d3
- affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 – < 8f4127a93cf60d561ad39849a9ac763ba0e14db5
- affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 – < d5e4586546974179feca305a94e07fac3e9727fe
- affected 2.6.32
- unaffected < 2.6.32
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/6eb4bd50be53f5afbabb3a3b5153276e08fa7a4a (opens in a new tab)
- https://git.kernel.org/stable/c/ce2a3be6909462f49c34de96be71f0ad5f0d573f (opens in a new tab)
- https://git.kernel.org/stable/c/6bdf4dcff98df634e04ebf99f52027a48d7f78ff (opens in a new tab)
- https://git.kernel.org/stable/c/0ec738a0d361d7eb37188117166d201f9df622d3 (opens in a new tab)
- https://git.kernel.org/stable/c/8f4127a93cf60d561ad39849a9ac763ba0e14db5 (opens in a new tab)
- https://git.kernel.org/stable/c/d5e4586546974179feca305a94e07fac3e9727fe (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86192 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93805)Record last updated .