CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ
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.
Metrics
- CVSS v3.1
- 8.8
- Severity
- HIGH
- Fixed in
- 0
- Affected Products
- 2
Fix available
- Linux / Linux< 10a7a702542240d5edb2b39450ac951c59ccd009 (from 15f02b91056253e8cdc592888f431da0731337b8) · < 46e5b71666fb7652082e4e214a3365f4b14f1dc3 (from 15f02b91056253e8cdc592888f431da0731337b8) · < fb4a3a26483f3ea2cd21c7a2f7c45d5670600465 (from 15f02b91056253e8cdc592888f431da0731337b8) · < 2124d82fd25e1671bb3ceb37998af5aae5903e06 (from 15f02b91056253e8cdc592888f431da0731337b8) · < 6b949a6b33cbdf621d9fc6f0c48ac00915dbf514 (from 15f02b91056253e8cdc592888f431da0731337b8) · < 8d0d94f8ba5b3a0beec3b0da558b9bea48018117 (from 15f02b91056253e8cdc592888f431da0731337b8)
- Linux / Linux5.7Fixed in 0, 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10, 7.0
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H