CVE-2024-50044

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