CVE-2023-53016
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2023-53016
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53016.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2023-53016
- Related
- Published
- 2025-03-27T17:15:50Z
- Modified
- 2025-04-15T19:41:27Z
- Downstream
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: Fix possible deadlock in rfcommskstate_change
syzbot reports a possible deadlock in rfcommskstatechange [1]. While rfcommsockconnect acquires the sk lock and waits for the rfcomm lock, rfcommsock_release could have the rfcomm lock and hit a deadlock for acquiring the sk lock. Here's a simplified flow:
rfcommsockconnect: locksock(sk) rfcommdlcopen: rfcommlock()
rfcommsockrelease: rfcommsockshutdown: rfcommlock() _rfcommdlcclose: rfcommkstatechange: locksock(sk)
This patch drops the sk lock before calling rfcommdlcopen to avoid the possible deadlock and holds sk's reference count to prevent use-after-free after rfcommdlcopen completes.
- References
Affected packages
Debian:12 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source