Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change

Vulnerability Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change rfcomm_sk_state_change attempts to use sock_lock so it must never be called with it locked but rfcomm_sock_ioctl always attempt to lock it causing the following trace: ====================================================== WARNING: possible circular locking dependency detected 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted ------------------------------------------------------ syz-executor386/5093 is trying to acquire lock: ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline] ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73 but task is already holding lock: ffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491

References

• https://git.kernel.org/stable/c/b77b3fb12fd483cae7c28648903b1d8a6b275f01
• https://git.kernel.org/stable/c/869c6ee62ab8f01bf2419e45326642be5c9b670a
• https://git.kernel.org/stable/c/ef44274dae9b0a90d1a97ce8b242a3b8243a7745
• https://git.kernel.org/stable/c/496b2ab0fd10f205e08909a125485fdc98843dbe
• https://git.kernel.org/stable/c/ced98072d3511b232ae1d3347945f35f30c0e303
• https://git.kernel.org/stable/c/38b2d5a57d125e1c17661b8308c0240c4a43b534
• https://git.kernel.org/stable/c/4cb9807c9b53bf1e5560420d26f319f528b50268
• https://git.kernel.org/stable/c/08d1914293dae38350b8088980e59fbc699a72fe