CVE-2026-68326wifi: mwifiex: bound uAP association event IEs to the event buffer
- 8.8HighCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% 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: mwifiex: bound uAP association event IEs to the event buffer mwifiex_process_uap_event() handles EVENT_UAP_STA_ASSOC by exposing the (re)association request IEs that the firmware copies into the event: sinfo->assoc_req_ies = &event->data[len]; len = (u8 *)sinfo->assoc_req_ies - (u8 *)&event->frame_control; sinfo->assoc_req_ies_len = le16_to_cpu(event->len) - (u16)len; event->len is supplied by the device firmware and is never validated, and the subtraction is unchecked. assoc_req_ies points into adapter->event_body[MAX_EVENT_SIZE], a fixed-size array embedded in the kmalloc()'d struct mwifiex_adapter. On the ap_11n_enabled path mwifiex_set_sta_ht_cap() walks these IEs with cfg80211_find_ie(), whose for_each_element() loop dereferences each element header. A firmware-reported event->len larger than the bytes actually received makes assoc_req_ies_len describe IEs that extend past event_body, so the walk reads out of the adapter slab object, a slab-out-of-bounds read (KASAN: slab-out-of-bounds in cfg80211_find_ie). An event->len smaller than the header instead makes the int subtraction negative, which wraps to a huge size_t when stored in assoc_req_ies_len. The same length is handed to cfg80211_new_sta(), so a more modest over-claim can also copy stale event_body bytes into the NL80211_CMD_NEW_STATION notification. A malicious or malfunctioning mwifiex device (USB/SDIO/PCIe) can deliver such an event while the interface is in AP/uAP mode. Validate event->len before use: reject a length that underflows the header or that would place the IEs outside the event_body[] buffer the event was copied into. event->len here is struct mwifiex_assoc_event.len, a payload field internal to this event, not the transport frame length, so it is validated in this handler rather than at the generic MWIFIEX_TYPE_EVENT receive path, which only sees the event cause and the transport frame length. The bound is against event_body[MAX_EVENT_SIZE] rather than the actually-received length because the transports store the event differently (USB and SDIO leave the 4-byte event header in event_skb, PCIe strips it via skb_pull), whereas event_body is the single fixed buffer all of them copy the event into. This is the event-path analogue of the receive-path bounds checks added in commit 119585281617 ("wifi: mwifiex: Fix OOB and integer underflow when rx packets").
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 2 months later
· 2 months 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected e568634ae7ac379661c90731d480e067929420a1 – < a616616b938f7922a93e79bef16b4643c57c0922
- affected e568634ae7ac379661c90731d480e067929420a1 – < 1ae00b6d9a6c82eb3de151d9b04ed59e06cc100f
- affected e568634ae7ac379661c90731d480e067929420a1 – < e7e93d3e8c240bdb70c41e79d169d74dfb442843
- affected e568634ae7ac379661c90731d480e067929420a1 – < a3f47d7c75ddad1a14621a309286f9fae3cba191
- affected e568634ae7ac379661c90731d480e067929420a1 – < ad26c75ae25749313248f06510ebe43b5bf4adcc
- affected e568634ae7ac379661c90731d480e067929420a1 – < d21464d93f8ba464dc3d7b4b31c6e0adcd9f659c
- affected e568634ae7ac379661c90731d480e067929420a1 – < b6766d7ea43edf5de9d5a572bc58b631d09efe4b
- affected e568634ae7ac379661c90731d480e067929420a1 – < f0858bfc7d3cab411a447b88e3ef970e575032c9
- affected 3.5
- unaffected < 3.5
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/a616616b938f7922a93e79bef16b4643c57c0922 (opens in a new tab)
- https://git.kernel.org/stable/c/1ae00b6d9a6c82eb3de151d9b04ed59e06cc100f (opens in a new tab)
- https://git.kernel.org/stable/c/e7e93d3e8c240bdb70c41e79d169d74dfb442843 (opens in a new tab)
- https://git.kernel.org/stable/c/a3f47d7c75ddad1a14621a309286f9fae3cba191 (opens in a new tab)
- https://git.kernel.org/stable/c/ad26c75ae25749313248f06510ebe43b5bf4adcc (opens in a new tab)
- https://git.kernel.org/stable/c/d21464d93f8ba464dc3d7b4b31c6e0adcd9f659c (opens in a new tab)
- https://git.kernel.org/stable/c/b6766d7ea43edf5de9d5a572bc58b631d09efe4b (opens in a new tab)
- https://git.kernel.org/stable/c/f0858bfc7d3cab411a447b88e3ef970e575032c9 (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-55427 (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-68326)Record last updated .