Bluetooth channel stall via signaling identifier exhaustion
Published Aug 15, 2026 · Updated Aug 15, 2026
Denial of service in affected Linux kernel versions allows physically proximate attackers to permanently stall a Bluetooth LE CoC channel. L2CAP allocates identifiers for response-free LE credit commands but never releases them, exhausts IDs 1–255, and then transmits invalid identifier 0. Reaching the flaw requires an established Bluetooth LE credit-based channel and sustained inbound data; the consequence is limited to that channel.
Summary
What happened
Denial of service in affected Linux kernel versions allows physically proximate attackers to permanently stall a Bluetooth LE CoC channel. L2CAP allocates identifiers for response-free LE credit commands but never releases them, exhausts IDs 1–255, and then transmits invalid identifier 0. Reaching the flaw requires an established Bluetooth LE credit-based channel and sustained inbound data; the consequence is limited to that channel.
The record
- CVE
- CVE-2026-72333
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-772, T1499
- Attack vector
- adjacent
- Privileges
- Unavailable
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=5.10.261 <5.11
- Affected versionversion=5.15.212 <5.16
- Affected versionversion=6.18.21 <6.18.40
- Affected versionversion=6.19.11 <6.20
- Affected versionversion=6c3ea155e5ee3e56606233acde8309afda66d483 <6e1930ece855a4c256f1c7e6632d634cfb9888b5
- Affected versionversion=6c3ea155e5ee3e56606233acde8309afda66d483 <d0a2b0c81f112540a337cde1c20251bf05ddf1da
- Affected versionversion=7.0
- Affected versionversion=84bc3197f7d87c5b89c156e853d0561a9154eceb
- Affected versionversion=8c1cdbc1bacc0cf9c27c3ebda11a81c3dcd01630
- Affected versionversion=9b24ad4787cad46a3917620799f8455c6533b8df <bd1e01170341291292fd4c46b5f6949da282ca6c
- Affected versionversion=e86554c37d3d2b4b24608e0313f882cae28b8adb <b8a32a5fc915b024c60f18d51b6cffd2bd64d4a6
- Affected versionversion=ea6cf86167b3972caa68972d2a1ad43ecbbb8331 <0c602cb8f148a36bfb39c25ade400bdadc023c4f
- Affected versionversion=ed97bb2cf96684ee646be6f37e4c4835f9d30caa
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