Linux kernel cfg80211 flaw affects widely deployed OS kernels and many Wi‑Fi clients; can disrupt systems and enable kernel compromise across devices.
CVE-2026-93806
Remote kernel memory corruption via crafted Wi‑Fi association response
Is CVE-2026-93806 being exploited?
Not confirmed. CVE-2026-93806 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.
How severe is CVE-2026-93806?
CVE-2026-93806 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-93806?
Yes. A fix has been recorded for CVE-2026-93806. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-93806 affect?
CVE-2026-93806 affects Linux kernel (cfg80211 Wi‑Fi stack), Linux laptops/desktops with Wi‑Fi, Embedded Linux devices and routers using cfg80211. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-93806?
Apply kernel updates/stable patches and update Wi‑Fi device firmware ASAP
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can send crafted Wi‑Fi assoc responses to trigger kernel memory corruption, causing DoS or possible kernel‑level code execution.
Immediate action required
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a57310600c1e2b9ada0f37c96e8f48aef47d3093
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 78ac450ad4624d6b2999cb4eeb28916767f81247
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < b760113aeca2e9362d56bf9e9263373ffe6c8eb3
- affected< 6.12.111
- affected< 6.18.53
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.