Adjacent kernel memory corruption via L2CAP locking race
Published Apr 3, 2026 · Updated Apr 3, 2026
Use-after-free in Linux Kernel Bluetooth L2CAP allows physically proximate attackers to corrupt kernel memory during connection teardown. l2cap_register_user() and l2cap_unregister_user() access conn->users and conn->hchan without conn->lock while l2cap_conn_del() tears down the same structure. Bluetooth L2CAP reachability and concurrent connection teardown are required; the documented outcomes are list corruption and access to freed connection state.
Summary
What happened
Use-after-free in Linux Kernel Bluetooth L2CAP allows physically proximate attackers to corrupt kernel memory during connection teardown. l2cap_register_user() and l2cap_unregister_user() access conn->users and conn->hchan without conn->lock while l2cap_conn_del() tears down the same structure. Bluetooth L2CAP reachability and concurrent connection teardown are required; the documented outcomes are list corruption and access to freed connection state.
The record
- CVE
- CVE-2026-23461
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=18ab6b6078fa8191ca30a3065d57bf35d5635761
- Affected versionversion=6.14
- Affected versionversion=ab4eedb790cae44313759b50fe47da285e2519d5 <71030f3b3015a412133a805ff47970cdcf30c2b8
- Affected versionversion=ab4eedb790cae44313759b50fe47da285e2519d5 <752a6c9596dd25efd6978a73ff21f3b592668f4a
- Affected versionversion=ab4eedb790cae44313759b50fe47da285e2519d5 <da3000cbe4851458a22be38bb18c0689c39fdd5f
- Affected versionversion=efc30877bd4bc85fefe98d80af60fafc86e5775e <11a87dd5df428a4b79a84d2790cac7f3c73f1f0d
- Affected versionversion=f87271d21dd4ee83857ca11b94e7b4952749bbae <c22a5e659959eb77c2fbb58a5adfaf3c3dab7abf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- syzbot L2CAP use-after-free reproducerproof of concept · demonstrated
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