Kernel memory corruption via unheld L2CAP channel
Published Aug 15, 2026 · Updated Aug 15, 2026
Linux kernel Bluetooth L2CAP use-after-free allows physically proximate attackers to corrupt kernel memory via a remote disconnect. l2cap_le_connect_rsp locks and operates on a channel returned by __l2cap_get_chan_by_ident without first retaining a reference, allowing concurrent deletion to free it. The path requires Bluetooth Low Energy L2CAP traffic and a concurrent disconnect; successful exploitation can crash the system or execute code in kernel context.
Summary
What happened
Linux kernel Bluetooth L2CAP use-after-free allows physically proximate attackers to corrupt kernel memory via a remote disconnect. l2cap_le_connect_rsp locks and operates on a channel returned by __l2cap_get_chan_by_ident without first retaining a reference, allowing concurrent deletion to free it. The path requires Bluetooth Low Energy L2CAP traffic and a concurrent disconnect; successful exploitation can crash the system or execute code in kernel context.
The record
- CVE
- CVE-2026-74540
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-825, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=3.14
- Affected versionversion=f1496dee9cbde2a62821f4441dadb0d3360f60c3 <09f447accc2570751e7d17f0dc0788b40d3edade
- Affected versionversion=f1496dee9cbde2a62821f4441dadb0d3360f60c3 <522b730c62c53a1981604fd73524697fd347830d
- Affected versionversion=f1496dee9cbde2a62821f4441dadb0d3360f60c3 <58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136
- Affected versionversion=f1496dee9cbde2a62821f4441dadb0d3360f60c3 <c4740e7f23ff9a8210198d8b4703259e21b9f69d
- Affected versionversion=f1496dee9cbde2a62821f4441dadb0d3360f60c3 <fd4c1e301bdec60a40728ea37de531cbccda501a
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.
Weakness, pattern, technique
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