CVE-2026-23395 Details
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.
A vulnerability in the Linux kernel's Bluetooth implementation, specifically within the Logical Link Control and Adaptation Protocol (L2CAP), has been addressed. The issue arose because the code accepted connection requests without considering the command identifier, leading to multiple requests being incorrectly marked as pending. This could result in allocating more than the maximum allowed connection identifiers, causing an overflow. The vulnerability affected the stable versions of the Linux kernel.
Users can update to the latest stable version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/10a7a702542240d5edb2b39450ac951c59ccd009 | kernel.org | Patch |
| https://git.kernel.org/stable/c/2124d82fd25e1671bb3ceb37998af5aae5903e06 | kernel.org | Patch |
| https://git.kernel.org/stable/c/46e5b71666fb7652082e4e214a3365f4b14f1dc3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5b3e2052334f2ff6d5200e952f4aa66994d09899 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6b949a6b33cbdf621d9fc6f0c48ac00915dbf514 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8d0d94f8ba5b3a0beec3b0da558b9bea48018117 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e72ee455297b794b852e5cea8d2d7bb17312172a | kernel.org | Patch |
| https://git.kernel.org/stable/c/fb4a3a26483f3ea2cd21c7a2f7c45d5670600465 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.7.1, < 5.10.253 >= 5.11, < 5.15.203 >= 5.16, < 6.1.167 >= 6.2, < 6.6.130 >= 6.7, < 6.12.78 >= 6.13, < 6.18.20 >= 6.19, < 6.19.10 5.7 - 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 24, 2026 | Initial Analysis | [email protected] |
| Apr 18, 2026 | CVE Modified | kernel.org |
| Apr 2, 2026 | CVE Modified | kernel.org |
| Mar 25, 2026 | New CVE Received | kernel.org |