Kernel compromise via unheld L2CAP channel
Published Sep 16, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel Bluetooth L2CAP before 6.5 allows physically proximate attackers to compromise or crash the kernel. l2cap_le_command_rej obtains a channel by identifier, then deletes and unlocks it without first holding a reference, allowing concurrent release. An established Bluetooth LE peer needs no pairing or encryption and can use a pending LE CoC identifier to trigger kernel memory access or panic.
Summary
What happened
Use-after-free in Linux kernel Bluetooth L2CAP before 6.5 allows physically proximate attackers to compromise or crash the kernel. l2cap_le_command_rej obtains a channel by identifier, then deletes and unlocks it without first holding a reference, allowing concurrent release. An established Bluetooth LE peer needs no pairing or encryption and can use a pending LE CoC identifier to trigger kernel memory access or panic.
The record
- CVE
- CVE-2023-53305
- Published
- Sep 16, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=71fb419724fadab4efdf98210aa3fe053bd81d29 <149daab45922ab1ac7f0cbeacab7251a46bf5e63
- Affected versionversion=71fb419724fadab4efdf98210aa3fe053bd81d29 <1a40c56e8bff3e424724d78a9a6b3272dd8a371d
- Affected versionversion=71fb419724fadab4efdf98210aa3fe053bd81d29 <255be68150291440657b2cdb09420b69441af3d8
- Affected versionversion=71fb419724fadab4efdf98210aa3fe053bd81d29 <2958cf9f805b9f0bdc4a761bf6ea281eb8d44f8e
- Affected versionversion=71fb419724fadab4efdf98210aa3fe053bd81d29 <548a6b64b3c0688f01119a6fcccceb41f8c984e4
- Affected versionversion=71fb419724fadab4efdf98210aa3fe053bd81d29 <e76bab1b7afa580cd76362540fc37551ada4359b
- Affected versionversion=71fb419724fadab4efdf98210aa3fe053bd81d29 <f752a0b334bb95fe9b42ecb511e0864e2768046f
- Affected versionversion=71fb419724fadab4efdf98210aa3fe053bd81d29 <fe49aa73cca6608714477b74bfc6874b9db979df
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
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