Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 15f02b91056253e8cdc592888f431da0731337b8 · < dc89961b76f12aff47124c1df4bdb32a080f4d0c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp
l2cap_ecred_reconf_rsp() calls l2cap_chan_del() without holding l2cap_chan_lock(). Every other l2cap_chan_del() caller in the file acquires the lock first. A remote BLE device can send a crafted L2CAP ECRED reconfiguration response to corrupt the channel list while another thread is iterating it.
Add l2cap_chan_hold() and l2cap_chan_lock() before l2cap_chan_del(), and l2cap_chan_unlock() and l2cap_chan_put() after, matching the pattern used in l2cap_ecred_conn_rsp() and l2cap_conn_del().
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP code deletes a channel without holding the required lock. A remote BLE device can send a crafted ECRED reconfiguration response that corrupts the channel list while another thread iterates it. The input does not specify authentication or user-interaction requirements.
Operators running Linux kernels with the affected Bluetooth L2CAP code should check their exposure; affected versions were not provided.