Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 15f02b91056253e8cdc592888f431da0731337b8 · < 8d0d94f8ba5b3a0beec3b0da558b9bea48018117| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP code can accept successive connection requests with the same identifier. A Bluetooth peer sending such requests can cause too many channels to be allocated, resulting in an overflow. The input does not specify whether authentication or user interaction is required.
Engineers running Linux kernels with Bluetooth L2CAP should check whether their kernel includes the fix; affected versions are not specified.