Kernel crash or code execution via L2CAP use-after-free
Published Jul 25, 2026 · Updated Jul 25, 2026
Use-after-free in Linux Kernel Bluetooth L2CAP allows physically proximate attackers to crash the kernel via connection teardown. The asynchronous l2cap_chan_timeout worker locks chan->conn after teardown frees the connection because the channel did not retain a connection reference. The race requires teardown while the timeout is running or pending, and the resulting memory corruption permits arbitrary code execution.
Summary
What happened
Use-after-free in Linux Kernel Bluetooth L2CAP allows physically proximate attackers to crash the kernel via connection teardown. The asynchronous l2cap_chan_timeout worker locks chan->conn after teardown frees the connection because the channel did not retain a connection reference. The race requires teardown while the timeout is running or pending, and the resulting memory corruption permits arbitrary code execution.
The record
- CVE
- CVE-2026-64434
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-364, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3634cbdc2eb414b69ffa752ddbe5e0458518e321
- Affected versionversion=50dfec218808b148ab4247b1858031b7a32015c5 <0b0e2bf39cf99e458d991b9df253727e036a7d7d
- Affected versionversion=5.10.259 <5.11
- Affected versionversion=5.15.210 <5.16
- Affected versionversion=6.1.176 <6.2
- Affected versionversion=6.12.93 <6.12.97
- Affected versionversion=6.18.35 <6.18.39
- Affected versionversion=6.6.143 <6.6.145
- Affected versionversion=7.0.12 <7.1
- Affected versionversion=7.1
- Affected versionversion=7555fd885a0603f50e49a655850a1f2bd8a25398
- Affected versionversion=859d3ace791ed878ae9ba5522c7844d960da8f88 <d3b739db5dc6f688a60d56da872fabaf65246032
- Affected versionversion=89dec92041717b027216e110599e4f6d6c921b79 <91047a4396a8b1857a6f712a90cf33ec0012b189
- Affected versionversion=8c8e620467a7b51562dbcefbd1f09f288d7d710d <50c38d9f42a529691e4e67ea9cedf4f0bfc8d277
- Affected versionversion=8c8e620467a7b51562dbcefbd1f09f288d7d710d <b66774b48dd98f07254951f74ea6f513efe7ff8b
- Affected versionversion=deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9
- Affected versionversion=e1c100e2d61bd8c718b7d91fe3e050780a9bf72d
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo