CVE-2023-53016
Last modified
CVE-2023-53016 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.15, < 5.15.91 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.9 | — |
| Linux | Linux Kernel | 6.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53016?
How severe is CVE-2023-53016?
How do I fix CVE-2023-53016?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53010In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53011In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53012In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53013In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53014In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53015In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53017In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53018In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53019In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-5302A vulnerability, which was classified as problematic, has be…5.4
- CVE-2023-53020In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2023-53021In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2023-53016?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST