CVE-2023-53016

Source
https://cve.org/CVERecord?id=CVE-2023-53016
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53016.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2023-53016
Downstream
Related
Published
2025-03-27T16:43:44.528Z
Modified
2026-03-12T03:20:29.805224Z
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
Bluetooth: Fix possible deadlock in rfcomm_sk_state_change
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: rfcomm_lock() __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.

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53016.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
1804fdf6e494e5e2938c65d8391690b59bcff897
Fixed
98aec50ff7f60cc6f2d6a4396b475c547e58b04d
Fixed
17511bd84871f4a6106cb335616e086880313f3f
Fixed
1d80d57ffcb55488f0ec0b77928d4f82d16b6a90

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53016.json"