Skip to content
Systems

CVE-2026-64557

8.8
High
EPSS 0.24%Patch availableJul 30, 2026

Linux kernel Bluetooth L2CAP use-after-free allows kernel crash or possible RCE via Bluetooth.

common questions

Is CVE-2026-64557 being exploited?

Not confirmed. CVE-2026-64557 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-64557?

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

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

What does CVE-2026-64557 affect?

CVE-2026-64557 affects Linux kernel (Bluetooth L2CAP), Linux desktops/laptops with Bluetooth, Embedded Linux/IoT devices with Bluetooth. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64557?

Update Linux kernel to fixed release or disable Bluetooth 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 (Bluetooth L2CAP)Linux desktops/laptops with BluetoothEmbedded Linux/IoT devices with Bluetooth
impact

Remote use-after-free via Bluetooth L2CAP can crash the kernel (DoS) and may enable local privilege escalation or remote code execution via crafted connections.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 8ffb929098a56939ac71509302eeab5b207bf262 and < b39298044e5534612511a2ff5de03ba5f6e7a820
  • affected>= 8ffb929098a56939ac71509302eeab5b207bf262 and < 8c37e4338c801ebb8cee52436c01c41e009f6e87
  • affected>= 8ffb929098a56939ac71509302eeab5b207bf262 and < 84e718b6a814edc84159361f9f454a4e92ae91ae
  • affected>= 8ffb929098a56939ac71509302eeab5b207bf262 and < 36da806f7fbaee56ad9e81859deec203f9728700
  • affected>= 8ffb929098a56939ac71509302eeab5b207bf262 and < 733e76e74e406c1d1ddc7369420dd8a47f48bb8a
  • affected>= 8ffb929098a56939ac71509302eeab5b207bf262 and < 6fef032af0092ed5ccb767239a9ac1bc38c08a40
  • affected3.13
vendor says fixed in< 3.13, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 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