Skip to content
Systems

CVE-2026-64178

HIGH
High
EPSS 0.25%Patch availableJul 21, 2026

Linux kernel Bluetooth bnep use-after-free allowing kernel memory corruption/DoS.

common questions

Is CVE-2026-64178 being exploited?

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

How severe is CVE-2026-64178?

CVE-2026-64178 is rated High. 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-64178?

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

What does CVE-2026-64178 affect?

CVE-2026-64178 affects Linux kernel (Bluetooth bnep subsystem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64178?

Apply kernel security updates, restrict CAP_NET_ADMIN, reboot affected hosts.

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

executive summary
technical analysis
affected
Linux kernel (Bluetooth bnep subsystem)
impact

Local attacker with CAP_NET_ADMIN can trigger a use-after-free in bnep leading to kernel crash (DoS) or memory corruption; race needed for further exploitation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a75bbcb10cb21acc169b785e9804f57d97873a9c
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 4907596f25b1720fa948371ac5f6c1f8da10a5bc
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 915a92182e2cda9cd7d2479020a44c6eda986f7c
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < fe69f634b076ae3ca81c5a5b845d9bba527036f7
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < b21805258d7e926adfd455fc820a447b90da3b82
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 5506aec795135cdd4cbf4e845929155663b25055
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e7578529b97e5d4e439cf8f3e637c2303015338f
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 59e932ded949fa6f0340bf7c6d7818f962fa4fd2
  • affected2.6.12
vendor says fixed in< 2.6.12, >= 5.10.258 and <= 5.10.*, >= 5.15.209 and <= 5.15.*, >= 6.1.175 and <= 6.1.*, >= 6.6.142 and <= 6.6.*, >= 6.12.92 and <= 6.12.*, >= 6.18.34 and <= 6.18.*, >= 7.0.11 and <= 7.0.*, >= 7.1 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