First published: Thu Mar 27 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix possible deadlock in rfcomm_sk_state_change 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's a simplified flow: rfcomm_sock_connect: lock_sock(sk) rfcomm_dlc_open: rfcomm_lock() rfcomm_sock_release: rfcomm_sock_shutdown: rfcomm_lock() __rfcomm_dlc_close: rfcomm_k_state_change: lock_sock(sk) This patch drops the sk lock before calling rfcomm_dlc_open to avoid the possible deadlock and holds sk's reference count to prevent use-after-free after rfcomm_dlc_open completes.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-53016 is categorized as a potential deadlock vulnerability in the Linux kernel's Bluetooth implementation.
To resolve CVE-2023-53016, ensure your Linux kernel is updated to the latest patched version that addresses this vulnerability.
CVE-2023-53016 affects the Linux kernel specifically related to Bluetooth rfcomm functionality.
Exploitation of CVE-2023-53016 could lead to a deadlock condition, potentially affecting system stability during Bluetooth operations.
As of now, there have been no reported active exploits for CVE-2023-53016, but it is advisable to patch the vulnerability promptly.