CVE-2026-68471
Linux kernel Wi‑Fi MLE length validation bug enabling remote kernel memory corruption.
Is CVE-2026-68471 being exploited?
Not confirmed. CVE-2026-68471 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-68471?
CVE-2026-68471 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-68471?
Yes. A fix has been recorded for CVE-2026-68471. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68471 affect?
CVE-2026-68471 affects Linux kernel (mac80211/ieee80211 Wi-Fi MLE), Linux-based routers, access points, and embedded/IoT devices using mac80211, Workstations and servers running affected Linux kernels with Wi‑Fi. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68471?
Install vendor kernel security updates; disable Wi‑Fi or restrict wireless access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can send crafted MLE Wi‑Fi frames to trigger kernel memory corruption, causing crashes or potential kernel RCE/privilege escalation.
Patch when possible
- affected>= 0f48b8b88aa9ed7b65d7cb55dbc57ec914ddada1 and < 90576bd6921a91eb038bffbb4b9467c2dc26aa1d
- affected>= 0f48b8b88aa9ed7b65d7cb55dbc57ec914ddada1 and < 2b1589fd9a076727a73bfb39e96622a76415ad32
- affected>= 0f48b8b88aa9ed7b65d7cb55dbc57ec914ddada1 and < 293baeae9b2434a3e432629d7720b5603db2d77e
- affected6.0
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.