Linux kernel mac80211 is a core, widely deployed networking component; RCE in the Wi‑Fi stack can lead to broad, high‑impact compromises across devices and infrastructure.
CVE-2026-68470
Remote kernel compromise via crafted Wi‑Fi extension frames in Linux mac80211
Is CVE-2026-68470 being exploited?
Not confirmed. CVE-2026-68470 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-68470?
CVE-2026-68470 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-68470?
Yes. A fix has been recorded for CVE-2026-68470. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68470 affect?
CVE-2026-68470 affects Linux kernel mac80211-enabled systems, Wi‑Fi clients, APs, and routers using affected kernels, Embedded/IoT devices and smartphones running affected Linux kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68470?
Install kernel and firmware updates immediately; restrict/segment wireless access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel code execution or crash via crafted 802.11 extension frames over Wi‑Fi, enabling full system compromise and privilege escalation.
Immediate action required
- affected>= 09a740ce352e1a1d16b9984115514ba9a4f4704b and < 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed
- affected>= 09a740ce352e1a1d16b9984115514ba9a4f4704b and < 57d503ce32eccfa7650065ca4c560f7e29a2e676
- affected5.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.