CVE-2026-64030
Wi‑Fi 7 AP can crash Linux clients via mac80211 EPCS link_id out‑of‑bounds (kernel DoS)
Is CVE-2026-64030 being exploited?
Not confirmed. CVE-2026-64030 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-64030?
CVE-2026-64030 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-64030?
Yes. A fix has been recorded for CVE-2026-64030. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64030 affect?
CVE-2026-64030 affects Linux kernel mac80211 (affected versions), Wi‑Fi 7 client devices running Linux, Embedded Linux devices with mac80211 Wi‑Fi, Linux-based routers with Wi‑Fi 7 support. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64030?
Apply kernel/mac80211 updates immediately; avoid/untrusted Wi‑Fi APs and update device firmware.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel crash (denial of service) via crafted EPCS Enable Response with link_id=15 from a Wi‑Fi 7 AP; attacker-controlled AP can crash affected clients.
Patch when possible
- affected>= de86c5f60839dc0d771711a848b4f55ad3f90844 and < 2d8379834800c30602f24c71ab7c40f5fe84d200
- affected>= de86c5f60839dc0d771711a848b4f55ad3f90844 and < 863f1f02a3bd70dbd857b8ac4070292fde8cb4e2
- affected>= de86c5f60839dc0d771711a848b4f55ad3f90844 and < f718506edd2d9c6a308ded9d13c632bf7b7d5a2c
- affected6.15
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.