https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 08:27:28 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53016 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: Fix possible deadlock in rfcomm_sk_state_change</p> <p>syzbot reports a possible deadlock in rfcomm_sk_state_change [1]. While rfcomm_sock_connect acquires the sk lock and waits for the rfcomm lock, rfcomm_sock_release could have the rfcomm lock and hit a deadlock for acquiring the sk lock. Here&#39;s a simplified flow:</p> <p>rfcomm_sock_connect: lock_sock(sk) rfcomm_dlc_open: rfcomm_lock()</p> <p>rfcomm_sock_release: rfcomm_sock_shutdown: rfcomm_lock() __rfcomm_dlc_close: rfcomm_k_state_change: lock_sock(sk)</p> <p>This patch drops the sk lock before calling rfcomm_dlc_open to avoid the possible deadlock and holds sk&#39;s reference count to prevent use-after-free after rfcomm_dlc_open completes.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: Fix possible deadlock in rfcomm_sk_state_change</p> <p>syzbot reports a possible deadlock in rfcomm_sk_state_change [1]. While rfcomm_sock_connect acquires the sk lock and waits for the rfcomm lock, rfcomm_sock_release could have the rfcomm lock and hit a deadlock for acquiring the sk lock. Here&#39;s a simplified flow:</p> <p>rfcomm_sock_connect: lock_sock(sk) rfcomm_dlc_open: rfcomm_lock()</p> <p>rfcomm_sock_release: rfcomm_sock_shutdown: rfcomm_lock() __rfcomm_dlc_close: rfcomm_k_state_change: lock_sock(sk)</p> <p>This patch drops the sk lock before calling rfcomm_dlc_open to avoid the possible deadlock and holds sk&#39;s reference count to prevent use-after-free after rfcomm_dlc_open completes.</p> https://vulnerability.circl.lu/vuln/cve-2023-53016