CVE-2026-64406
Linux kernel Bluetooth use-after-free in L2CAP socket cleanup
Is CVE-2026-64406 being exploited?
Not confirmed. CVE-2026-64406 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-64406?
CVE-2026-64406 is rated High with a CVSS score of 8.0. 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-64406?
Yes. A fix has been recorded for CVE-2026-64406. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64406 affect?
CVE-2026-64406 affects Linux kernel (Bluetooth L2CAP subsystem), Ubuntu, Debian, Red Hat Enterprise Linux, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64406?
Apply vendor kernel updates or disable Bluetooth if unused.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Nearby or local attacker with Bluetooth access can trigger kernel memory corruption, causing crashes or possible local privilege escalation.
Patch when possible
- affected>= 751de6ec671fe75ad9cf65a0638d2a06b6a5984d and < c0577c55219be42b6ea2ea8db11e85bfab6f4e8d
- affected>= 407217734835d21d4e0105ebf347860dc1806f88 and < 96ad400d5132eb333f28f6f1e2d58f0728ca9547
- affected>= 7eebd4c2c86f573af87ff165d08a83432eb0b919 and < 0a98ff4e7b867f72fbb4e1237d81e9fa02ded0a0
- affected>= 5d86d2f1b4d9a508c441d3e45277ae1a73cfed57 and < c66a95e60b65d876a927123b0ed36bd6177d9ca6
- affected>= 87c543e2f78d0871f271df92dab98901bbd5b6f5 and < 6303ed4bbe0095f4cc195225479bf506e010d1db
- affected>= added1213395071470a900cc845a042fb51882a6 and < 26168db1ce5a9766cde021b18e590a101c056614
- affected>= ab1513597c6cf17cd1ad2a21e3b045421b48e022 and < 50c662bdcd51b03033a0abed6716bfd377ba1049
- affected>= ab1513597c6cf17cd1ad2a21e3b045421b48e022 and < 4bd0b274054f2679f28b70222b607bb0afc3ab9a
- affecteda5ca86a6097a8b030ca3226cd300b17ed330f966
- affected>= 5.10.259 and < 5.10.261
- affected>= 5.15.210 and < 5.15.212
- affected>= 6.1.175 and < 6.1.178
- affected>= 6.6.142 and < 6.6.145
- affected>= 6.12.92 and < 6.12.96
- affected>= 6.18.34 and < 6.18.39
- affected>= 7.0.11 and < 7.1
- affected7.1
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.