AZL-80705
See a problem?- Import Source
- https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-80705.json
- JSON Data
- https://api.osv.dev/v1/vulns/AZL-80705
- Upstream
- Published
- 2026-03-25T11:16:40Z
- Modified
- 2026-08-28T17:46:33.175440972Z
- Summary
- CVE-2026-23395 affecting package kernel for versions less than 6.6.130.1-1
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Fix accepting multiple L2CAPECREDCONN_REQ
Currently the code attempts to accept requests regardless of the command identifier which may cause multiple requests to be marked as pending (FLAGDEFERSETUP) which can cause more than L2CAPECREDMAXCID(5) to be allocated in l2capecredrspdefer 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.
- References