wifi: cfg80211: validate rx/tx MLME callback frame lengths before access
Summary
| CVE | CVE-2026-93805 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-24 17:17:13 UTC |
| Updated | 2026-10-03 11:17:50 UTC |
| 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. |
Risk And Classification
EPSS: 0.001730000 probability, percentile 0.060190000 (date 2026-10-05)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 6eb4bd50be53f5afbabb3a3b5153276e08fa7a4a git | Not specified |
| CNA | Linux | Linux | affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 ce2a3be6909462f49c34de96be71f0ad5f0d573f git | Not specified |
| CNA | Linux | Linux | affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 6bdf4dcff98df634e04ebf99f52027a48d7f78ff git | Not specified |
| CNA | Linux | Linux | affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 0ec738a0d361d7eb37188117166d201f9df622d3 git | Not specified |
| CNA | Linux | Linux | affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 8f4127a93cf60d561ad39849a9ac763ba0e14db5 git | Not specified |
| CNA | Linux | Linux | affected 6829c878ecd24ff0ae41b4668c7e9d0f11b66942 d5e4586546974179feca305a94e07fac3e9727fe git | Not specified |
| CNA | Linux | Linux | affected 2.6.32 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.32 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.222 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.189 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.158 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/ce2a3be6909462f49c34de96be71f0ad5f0d573f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d5e4586546974179feca305a94e07fac3e9727fe | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6eb4bd50be53f5afbabb3a3b5153276e08fa7a4a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6bdf4dcff98df634e04ebf99f52027a48d7f78ff | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0ec738a0d361d7eb37188117166d201f9df622d3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8f4127a93cf60d561ad39849a9ac763ba0e14db5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.