Kernel compromise via L2CAP lock imbalance
Published Sep 16, 2025 · Updated Sep 16, 2025
A lock imbalance in the Linux kernel Bluetooth L2CAP handler allows physically proximate attackers to crash or compromise the kernel. l2cap_disconnect_rsp calls l2cap_get_chan_by_scid without first acquiring conn->chan_lock, then unlocks that lock when a crafted response supplies a nonexistent SCID. An unauthenticated Bluetooth peer within radio range can reach the path on an established ACL or LE link, causing a warning or racing channel-list operations into use-after-free access.
Summary
What happened
A lock imbalance in the Linux kernel Bluetooth L2CAP handler allows physically proximate attackers to crash or compromise the kernel. l2cap_disconnect_rsp calls l2cap_get_chan_by_scid without first acquiring conn->chan_lock, then unlocks that lock when a crafted response supplies a nonexistent SCID. An unauthenticated Bluetooth peer within radio range can reach the path on an established ACL or LE link, causing a warning or racing channel-list operations into use-after-free access.
The record
- CVE
- CVE-2023-53297
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <116b9c002c894097adc2b8684db2d1da4229ed46
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2112c4c47d36bc5aba3ddeb9afedce6ae6a67e7d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <25e97f7b1866e6b8503be349eeea44bb52d661ce
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5134556c9be582793f30695c09d18a26fe1ff2d7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <55410a9144c76ecda126e6cdec556dfcd8f343b2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5f352a56f0e607e6ff539cbf12156bfd8af232be
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6a27762340ad08643de3bc17fe1646ea489ca2e2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd269a0435f8e9943b7a57c5a59688848d42d449
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
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