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.' So this attempts to check if there are any channels pending with the same identifier and rejects if any are found. The Linux kernel CVE team has assigned CVE-2026-23395 to this issue.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 15f02b91056253e8cdc592888f431da0731337b8, 5.7, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10, 7.0-rc5 |
Updated severity from HIGH to CRITICAL and changed patch available version to 7.0-rc4.
Updated description with CVE-2026-23395, added affected versions, changed severity to HIGH, and marked exploit available and actively exploited.
Initial creation
