In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid…

Why it is Yellow

• CVSS 7.5 high
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/18174b166547ef41973cc19feb5ef9cab39a8def
• https://git.kernel.org/stable/c/4aafb47301a799d3e01230d6568c4e93524e1523
• https://git.kernel.org/stable/c/801fb950cae7048eb7d83b18857d1ca37b8cd5a4
• https://git.kernel.org/stable/c/bfce253f039eb5f58b810af267942a9f59207254
• https://git.kernel.org/stable/c/c6792c441767256030606eb82dca5d5fc360dd9a
• https://git.kernel.org/stable/c/c741977e413f5b49d306700820fb55ccb8269f5a
• https://git.kernel.org/stable/c/eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c

Original description

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.