Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b7ce436a5d798bc59e71797952566608a4b4626b · fixed in eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c; From b7ce436a5d798bc59e71797952566608a4b4626b · fixed in 4aafb47301a799d3e01230d6568c4e93524e1523; From b7ce436a5d798bc59e71797952566608a4b4626b · fixed in c741977e413f5b49d306700820fb55ccb8269f5a; From b7ce436a5d798bc59e71797952566608a4b4626b · fixed in c6792c441767256030606eb82dca5d5fc360dd9a; From b7ce436a5d798bc59e71797952566608a4b4626b · fixed in bfce253f039eb5f58b810af267942a9f59207254; From b7ce436a5d798bc59e71797952566608a4b4626b · fixed in 18174b166547ef41973cc19feb5ef9cab39a8def; From b7ce436a5d798bc59e71797952566608a4b4626b · fixed in 801fb950cae7048eb7d83b18857d1ca37b8cd5a4
- Linux Linux
5.15
- KernelLinux
From 5.15.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 7
git.kernel.org
- stable/c/eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c
- stable/c/4aafb47301a799d3e01230d6568c4e93524e1523
- stable/c/c741977e413f5b49d306700820fb55ccb8269f5a
- stable/c/c6792c441767256030606eb82dca5d5fc360dd9a
- stable/c/bfce253f039eb5f58b810af267942a9f59207254
- stable/c/18174b166547ef41973cc19feb5ef9cab39a8def
- stable/c/801fb950cae7048eb7d83b18857d1ca37b8cd5a4