Adjacent service hang via Bluetooth socket deadlock
Published Apr 17, 2024 · Updated Jun 1, 2026
Deadlock in the Linux kernel Bluetooth socket layer allows remote attackers to hang affected systems through crafted L2CAP traffic. bt_sock_ioctl takes the socket lock while receive handling can enter l2cap_sock_recv_cb and attempt to acquire that lock again, blocking hci_rx_work. Reachability requires an enabled, reachable Bluetooth L2CAP path from an adjacent attacker, and the bounded consequence is a service hang rather than data disclosure or modification.
Summary
What happened
Deadlock in the Linux kernel Bluetooth socket layer allows remote attackers to hang affected systems through crafted L2CAP traffic. bt_sock_ioctl takes the socket lock while receive handling can enter l2cap_sock_recv_cb and attempt to acquire that lock again, blocking hci_rx_work. Reachability requires an enabled, reachable Bluetooth L2CAP path from an adjacent attacker, and the bounded consequence is a service hang rather than data disclosure or modification.
The record
- CVE
- CVE-2024-26886
- Published
- Apr 17, 2024
- Updated
- Jun 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- Jun 1, 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=1d576c3a5af850bf11fbd103f9ba11aa6d6061fb <64be3c6154886200708da0dfe259705fb992416c
- Affected versionversion=2b16d960c79abc397f102c3d23d30005b68cb036 <60673f442984fe689d4127a5dd4be414247b3d67
- Affected versionversion=2e07e8348ea454615e268222ae3fc240421be768 <2c9e2df022ef8b9d7fac58a04a2ef4ed25288955
- Affected versionversion=2e07e8348ea454615e268222ae3fc240421be768 <817e8138ce86001b2fa5c63d6ede756e205a01f7
- Affected versionversion=2e07e8348ea454615e268222ae3fc240421be768 <f7b94bdc1ec107c92262716b073b3e816d4784fb
- Affected versionversion=37f71e2c9f515834841826f4eb68ec33cfb2a1ff
- Affected versionversion=5.10.206 <5.11
- Affected versionversion=5.15.146 <5.15.209
- Affected versionversion=6.1.70 <6.2
- Affected versionversion=6.6.9 <6.6.23
- Affected versionversion=6.7
- Affected versionversion=db1b14eec8c61a20374de9f9c2ddc6c9406a8c42
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