Skip to content
Systems

CVE-2026-64255

8.8
High
EPSS 0.22%Patch availableJul 27, 2026

iwlwifi kernel OOB access via BA handler can crash or compromise kernel

common questions

Is CVE-2026-64255 being exploited?

Not confirmed. CVE-2026-64255 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.22% probability of exploitation in the next 30 days.

How severe is CVE-2026-64255?

CVE-2026-64255 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-64255?

Yes. A fix has been recorded for CVE-2026-64255. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64255 affect?

CVE-2026-64255 affects Linux kernel (iwlwifi driver), Intel wireless NICs (iwlwifi), Linux-based devices with Intel Wi‑Fi (laptops, embedded). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64255?

Apply vendor/kernel updates with the iwlwifi fix or disable Wi‑Fi until patched

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (iwlwifi driver)Intel wireless NICs (iwlwifi)Linux-based devices with Intel Wi‑Fi (laptops, embedded)
impact

Out-of-bounds access in iwlwifi via crafted BA frames can crash the kernel or corrupt memory, enabling DoS or potential privilege escalation/remote code execution.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 9aa3856d9b6f3f8bf085b5bbb5f3703578bf452b and < 1de92789ce31e46fa7e7d8e89c90b19cdb1c103b
  • affected>= 9aa3856d9b6f3f8bf085b5bbb5f3703578bf452b and < fe7f339f63c9dc4ca546ed7ac38ba4bb3a99dcfc
  • affected>= 9aa3856d9b6f3f8bf085b5bbb5f3703578bf452b and < f056fc2b927448d37eca6b6cacc3d1b0f67b20d2
  • affected6.4
vendor says fixed in< 6.4, >= 6.18.38 and <= 6.18.*, >= 7.1.3 and <= 7.1.*, >= 7.2 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free