Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b7ce436a5d798bc59e71797952566608a4b4626b · < 18174b166547ef41973cc19feb5ef9cab39a8def| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
rfcomm_sock_cleanup_listen() closes unaccepted child sockets through rfcomm_sock_close(), which takes the child socket lock before rfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these locks in reverse order while handling connections and DLC state changes, so lockdep reports a possible deadlock.
Close dequeued children without taking their socket lock. The accept queue owns a reference to each child, and bt_accept_dequeue() locks the child while unlinking it and clearing its parent pointer.
Dropping the child lock makes it important to prevent a concurrent rfcomm_connect_ind() from enqueueing a new child after cleanup observes an empty queue. Set a listening socket to BT_CLOSED while its lock is still held, before dropping the lock and draining the queue. The state check in rfcomm_connect_ind() then rejects new children once cleanup starts.
From the CVE record · Linux
The Linux kernel’s Bluetooth RFCOMM listener cleanup can acquire locks in the opposite order from the RFCOMM worker, creating a possible deadlock during connection handling. The input does not establish whether an attacker can trigger it or specify authentication or user-interaction requirements.
Engineers running Linux kernels with Bluetooth RFCOMM should check their deployments; affected versions are not specified.