Skip to content
Systems

CVE-2026-64408

8.8
High
EPSS 0.26%Patch availableJul 27, 2026

Linux kernel Bluetooth use-after-free in bnep L2CAP during netdev registration.

common questions

Is CVE-2026-64408 being exploited?

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

How severe is CVE-2026-64408?

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

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

What does CVE-2026-64408 affect?

CVE-2026-64408 affects Linux kernel (Bluetooth bnep / bnep_add_connection), Linux distributions and devices with Bluetooth stacks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64408?

Apply vendor/kernel security updates and reboot; disable Bluetooth if immediate patching is impossible.

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 / bnep_add_connection)Linux distributions and devices with Bluetooth stacks
impact

Bluetooth-proximity use-after-free in kernel may cause panic (DoS) and could enable local privilege escalation or code execution.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < 390b5db3ff8745187f094c4e915663b7b1f98944
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < 46a88784c4c9b96954dd86f747ce93f65efa1302
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < 551ae773ec64045b4e72099132654887e0270bcc
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < ae215c5b6422d8eda443b861b124bd1be6969c31
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < df22adc7eafc22e651561813c11dc51a796b12ee
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < a6b22dbd80926556290ad2243be25218d6956a19
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < 563a8573047182f550b1e1e030615755cd8c41da
  • affected>= 65f53e9802dbfae0e5758a91793c3f5f8bece49b and < bb067a99a0356196c0b89a95721985485ebce5a5
  • affected3.13
vendor says fixed in< 3.13, >= 5.10.261 and <= 5.10.*, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.96 and <= 6.12.*, >= 6.18.39 and <= 6.18.*, >= 7.1.4 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