CVE-2026-72333: Bluetooth: L2CAP: fix tx ident leak for commands without a response
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 0c602cb8f148a36bfb39c25ade400bdadc023c4f, 5.11, 5.16.
Low priority for now. Upgrade to Linux Linux 0c602cb8f148a36bfb39c25ade400bdadc023c4f, 5.11, 5.16 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix tx ident leak for commands without a response Commit 6c3ea155e5ee ("Bluetooth: L2CAP: Fix not tracking outstanding TX ident") changed ident allocation to use an IDA, releasing idents in l2cap_put_ident() when the matching response command is received. But identifiers allocated for commands that have no response defined are never released. In particular L2CAP_LE_CREDITS is sent repeatedly for the lifetime of an LE CoC channel, so a peer streaming data to the host exhausts the 1-255 ident range after 254 credit packets. From then on l2cap_get_ident() fails: kernel: Bluetooth: Unable to allocate ident: -28 and every subsequent L2CAP_LE_CREDITS packet is sent with ident 0, which is invalid (Core Spec, Vol 3, Part A, Section 4: "Signaling identifier 0x00 is an invalid identifier and shall never be used in any command"). Remote stacks that validate the ident drop these commands, never receive new credits, and the channel stalls permanently. With default socket buffers this happens after roughly 0.5 MB of received data (the exact amount depends on the socket receive buffer): < ACL Data TX: Handle 2048 flags 0x00 dlen 12 LE L2CAP: LE Flow Control Credit (0x16) ident 0 len 4 Source CID: 64 Credits: 1 Release the ident immediately after sending L2CAP_LE_CREDITS since no response will ever release it. Use a local variable instead of chan->ident so that an ident that an EXT_FLOWCTL channel may be waiting on (e.g. a pending reconfigure) is not overwritten by a credit packet. Also add the missing L2CAP_LE_CONN_RSP case to l2cap_put_ident() so idents allocated for outgoing L2CAP_LE_CONN_REQ commands are released when the response arrives.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- ed97bb2cf96684ee646be6f37e4c4835f9d30caa, 84bc3197f7d87c5b89c156e853d0561a9154eceb, 8c1cdbc1bacc0cf9c27c3ebda11a81c3dcd01630, 7.0affected
- e86554c37d3d2b4b24608e0313f882cae28b8adb and later · before b8a32a5fc915b024c60f18d51b6cffd2bd64d4a6affected · git
- 9b24ad4787cad46a3917620799f8455c6533b8df and later · before bd1e01170341291292fd4c46b5f6949da282ca6caffected · git
- ea6cf86167b3972caa68972d2a1ad43ecbbb8331 and later · before 0c602cb8f148a36bfb39c25ade400bdadc023c4faffected · git
- 6c3ea155e5ee3e56606233acde8309afda66d483 and later · before d0a2b0c81f112540a337cde1c20251bf05ddf1daaffected · git
- 6c3ea155e5ee3e56606233acde8309afda66d483 and later · before 6e1930ece855a4c256f1c7e6632d634cfb9888b5affected · git
- 6.18.21 and later · before 6.18.40affected · semver
- 5.10.261 and later · before 5.11affected · semver
- 5.15.212 and later · before 5.16affected · semver
- 6.19.11 and later · before 6.20affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72328Aug 15, 2026 · accel/amdxdna: Fix potential amdxdna_umap lifetime race31Monitor
- ← EarlierCVE-2026-72332Aug 15, 2026 · accel/amdxdna: Prevent PM resume deadlock in hwctx_sync_debug_bo()0Monitor
- Later →CVE-2026-72340Aug 15, 2026 · net: microchip: vcap: fix races on the shared Super VCAP block31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0c602cb8f148a36bfb39c25ade400bdadc023c4f | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 6.18.40 | Vendor (CNA) |
| Linux Linux | 6.20 | Vendor (CNA) |
| Linux Linux | 6e1930ece855a4c256f1c7e6632d634cfb9888b5 | Vendor (CNA) |
| Linux Linux | b8a32a5fc915b024c60f18d51b6cffd2bd64d4a6 | Vendor (CNA) |
| Linux Linux | bd1e01170341291292fd4c46b5f6949da282ca6c | Vendor (CNA) |
| Linux Linux | d0a2b0c81f112540a337cde1c20251bf05ddf1da | Vendor (CNA) |
| debian:linux | 7.1.5-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.