CVE-2026-23395

Published: Mar 25, 2026 Last Modified: Mar 25, 2026
ExploitDB:
Other exploit source:
Google Dorks:

Description

AI Translation Available

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.

https://git.kernel.org/stable/c/2124d82fd25e1671bb3ceb37998af5aae5903e06
https://git.kernel.org/stable/c/5b3e2052334f2ff6d5200e952f4aa66994d09899
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/fb4a3a26483f3ea2cd21c7a2f7c45d5670600465