Adjacent memory corruption via duplicate L2CAP identifiers
Published Mar 25, 2026 · Updated Mar 25, 2026
Stack buffer overflow in Linux Kernel allows physically proximate attackers to corrupt kernel memory through Bluetooth L2CAP requests. The L2CAP request handler accepts repeated Enhanced Credit Based Connection Requests with the same command identifier, marks multiple channels pending, and lets l2cap_ecred_rsp_defer allocate beyond its five-CID stack array. Bluetooth radio proximity and no pairing or authentication are sufficient; the overflow can compromise kernel confidentiality, integrity, and availability.
Summary
What happened
Stack buffer overflow in Linux Kernel allows physically proximate attackers to corrupt kernel memory through Bluetooth L2CAP requests. The L2CAP request handler accepts repeated Enhanced Credit Based Connection Requests with the same command identifier, marks multiple channels pending, and lets l2cap_ecred_rsp_defer allocate beyond its five-CID stack array. Bluetooth radio proximity and no pairing or authentication are sufficient; the overflow can compromise kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-23395
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 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=15f02b91056253e8cdc592888f431da0731337b8 <2124d82fd25e1671bb3ceb37998af5aae5903e06
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <5b3e2052334f2ff6d5200e952f4aa66994d09899
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <6b949a6b33cbdf621d9fc6f0c48ac00915dbf514
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <8d0d94f8ba5b3a0beec3b0da558b9bea48018117
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <e72ee455297b794b852e5cea8d2d7bb17312172a
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <fb4a3a26483f3ea2cd21c7a2f7c45d5670600465
- Affected versionversion=5.7
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.
Weakness, pattern, technique
No sourced classifications are available.
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