Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f1496dee9cbde2a62821f4441dadb0d3360f60c3 · < 58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp
l2cap_le_connect_rsp() obtains a channel via __l2cap_get_chan_by_ident() but neither holds a reference nor uses l2cap_chan_hold_unless_zero() before locking and operating on it. A concurrent l2cap_chan_del() triggered by a remote disconnect can free the channel between the lookup and l2cap_chan_lock(), causing a use-after-free.
The BR/EDR counterpart l2cap_connect_rsp() and the sibling handler l2cap_le_command_rej() already use l2cap_chan_hold_unless_zero() to safely hold a reference, but l2cap_le_connect_rsp() was left unprotected.
Fix by adding l2cap_chan_hold_unless_zero() after the ident lookup and l2cap_chan_put() on the exit path, consistent with other L2CAP response handlers.
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP response handler can use a channel after it has been freed. This can occur when a remote disconnect deletes the channel between lookup and locking; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with the affected Bluetooth L2CAP handler should check their versions; affected versions are not specified.