CVE-2026-23395

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ<br /> <br /> Currently the code attempts to accept requests regardless of the<br /> command identifier which may cause multiple requests to be marked<br /> as pending (FLAG_DEFER_SETUP) which can cause more than<br /> L2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer<br /> causing an overflow.<br /> <br /> The spec is quite clear that the same identifier shall not be used on<br /> subsequent requests:<br /> <br /> &amp;#39;Within each signaling channel a different Identifier shall be used<br /> for each successive request or indication.&amp;#39;<br /> 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<br /> <br /> So this attempts to check if there are any channels pending with the<br /> same identifier and rejects if any are found.