# CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ

> A flaw in the Linux kernel Bluetooth L2CAP module allows remote attackers to cause a denial of service via multiple connection requests with the same identifier.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-80705, BELL-CVE-2026-23395, DEBIAN-CVE-2026-23395, GHSA-5r99-pj6c-hg6v, ROOT-OS-DEBIAN-11-CVE-2026-23395, ROOT-OS-DEBIAN-12-CVE-2026-23395, ROOT-OS-DEBIAN-13-CVE-2026-23395, ROOT-OS-UBUNTU-2204-CVE-2026-23395, ROOT-OS-UBUNTU-2404-CVE-2026-23395, UBUNTU-CVE-2026-23395

## What is CVE-2026-23395?

CVE-2026-23395 is a high-severity vulnerability in Linux kernel, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-23395?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-23395?

Apply the vendor's patch.

## Is CVE-2026-23395 being exploited?

There is no known exploitation of CVE-2026-23395 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23395 and fix it if it is affected.

What it is: CVE-2026-23395 is a high-severity vulnerability in Linux kernel, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23395 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23395/ (Markdown: https://insights.sbomify.com/CVE-2026-23395/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23395
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23395
- OSV: https://osv.dev/vulnerability/CVE-2026-23395

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23395/
Summaries are generated and may contain mistakes; the official description above is the record.