CWE
416
Advisory Published
Updated

CVE-2023-53016: Bluetooth: Fix possible deadlock in rfcomm_sk_state_change

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 SoftwareAffected VersionHow to fix
Linux Kernel

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2023-53016?

    CVE-2023-53016 is categorized as a potential deadlock vulnerability in the Linux kernel's Bluetooth implementation.

  • How do I fix CVE-2023-53016?

    To resolve CVE-2023-53016, ensure your Linux kernel is updated to the latest patched version that addresses this vulnerability.

  • Which software versions are affected by CVE-2023-53016?

    CVE-2023-53016 affects the Linux kernel specifically related to Bluetooth rfcomm functionality.

  • What are the risks associated with CVE-2023-53016?

    Exploitation of CVE-2023-53016 could lead to a deadlock condition, potentially affecting system stability during Bluetooth operations.

  • Is CVE-2023-53016 being actively exploited?

    As of now, there have been no reported active exploits for CVE-2023-53016, but it is advisable to patch the vulnerability promptly.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203