CVE-2026-68470wifi: mac80211: validate extension-frame layout before RX
- 8.8HighCVSS base score
- 0.31%Exploitation in 30 daysEPSS · top 76% 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: mac80211: validate extension-frame layout before RX Extension frames only have the extension header at the regular 802.11 header offset. The generic RX path can still reach helpers and interface dispatch code that read regular header address fields before unsupported extension subtypes are dropped. mac80211 currently only handles S1G beacon extension frames. Drop other extension subtypes before they can reach regular-header RX processing. For S1G beacons, linearize the SKB with the management-frame path and require the fixed S1G beacon header, including optional fixed fields indicated by frame control, before generic RX dispatch. Route S1G beacons through the station/default-link RX path without regular-header station lookup. Avoid regular-header address reads in the mac80211 RX paths that process S1G extension beacons, including accept-frame, duplicate-detection, address-copy, and MLO address-translation paths. Also make ieee80211_get_bssid() length-safe before returning the S1G source-address pointer.
Timeline
ID reserved
By Linux
- 16 days later
· 16 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.31% · top 76% of all CVEs (18 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 09a740ce352e1a1d16b9984115514ba9a4f4704b – < 7aba69b611007e11b9b93118ff8fe88998c3107f
- affected 09a740ce352e1a1d16b9984115514ba9a4f4704b – < 1c3d9c6bd5b795f3b952b40d574c8e424e14a39b
- affected 09a740ce352e1a1d16b9984115514ba9a4f4704b – < 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed
- affected 09a740ce352e1a1d16b9984115514ba9a4f4704b – < 57d503ce32eccfa7650065ca4c560f7e29a2e676
- affected 5.10
- unaffected < 5.10
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/7aba69b611007e11b9b93118ff8fe88998c3107f (opens in a new tab)
- https://git.kernel.org/stable/c/1c3d9c6bd5b795f3b952b40d574c8e424e14a39b (opens in a new tab)
- https://git.kernel.org/stable/c/625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed (opens in a new tab)
- https://git.kernel.org/stable/c/57d503ce32eccfa7650065ca4c560f7e29a2e676 (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-59092 (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-68470)Record last updated .