Affects ubiquitous Linux kernel wifi stack; widely deployed across servers and devices.
CVE-2026-46152
Linux kernel mac80211 race can corrupt packet handling.
Is CVE-2026-46152 being exploited?
Not confirmed. CVE-2026-46152 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.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-46152?
CVE-2026-46152 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-46152?
Yes. A fix has been recorded for CVE-2026-46152. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46152 affect?
CVE-2026-46152 affects Linux kernel (mac80211). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46152?
Update to patched kernel version
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker via crafted 802.11 frames may cause packet misprocessing or kernel crash.
Patch when possible
- affected>= 3468e1e0c639032a603450f0830ccabfa76f5806 and < 03584528bfffb195e384698af9148b94e42e3f14
- affected>= 3468e1e0c639032a603450f0830ccabfa76f5806 and < 1739fc31b4de06c5c78ce0741182770fb079091e
- affected>= 3468e1e0c639032a603450f0830ccabfa76f5806 and < e131562d6f2b958148c35c98831b007f47f0e3d3
- affected>= 3468e1e0c639032a603450f0830ccabfa76f5806 and < 3ef44f96ccc3e06e059dec57842e366f0c4b1893
- affected>= 3468e1e0c639032a603450f0830ccabfa76f5806 and < 7a5b81e0c87a075afd572f659d8eb68c9c4cd2ba
- affected6.4
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.