Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change rfcomm_sk_state_change attempts to use sock_lock so it must never be called with it locked but rfcomm_sock_ioctl always attempt to lock it causing the following trace: ====================================================== WARNING: possible circular locking dependency detected 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted ------------------------------------------------------ syz-executor386/5093 is trying to acquire lock: ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline] ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73 but task is already holding lock: ffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 3241ad820dbb172021e0268b5611031991431626 · fixed in b77b3fb12fd483cae7c28648903b1d8a6b275f01; From 3241ad820dbb172021e0268b5611031991431626 · fixed in 869c6ee62ab8f01bf2419e45326642be5c9b670a; From 3241ad820dbb172021e0268b5611031991431626 · fixed in ef44274dae9b0a90d1a97ce8b242a3b8243a7745; From 3241ad820dbb172021e0268b5611031991431626 · fixed in 496b2ab0fd10f205e08909a125485fdc98843dbe; From 3241ad820dbb172021e0268b5611031991431626 · fixed in ced98072d3511b232ae1d3347945f35f30c0e303; From 3241ad820dbb172021e0268b5611031991431626 · fixed in 38b2d5a57d125e1c17661b8308c0240c4a43b534; From 3241ad820dbb172021e0268b5611031991431626 · fixed in 4cb9807c9b53bf1e5560420d26f319f528b50268; From 3241ad820dbb172021e0268b5611031991431626 · fixed in 08d1914293dae38350b8088980e59fbc699a72fe
- Linux Linux
2.6.27
- KernelLinux
From 2.6.27 · fixed in 4.19.323; From 4.20.0 · fixed in 5.4.285; From 5.5.0 · fixed in 5.10.227; From 5.11.0 · fixed in 5.15.168; From 5.16.0 · fixed in 6.1.113; From 6.2.0 · fixed in 6.6.57; From 6.7.0 · fixed in 6.11.4
References 8
git.kernel.org
- stable/c/b77b3fb12fd483cae7c28648903b1d8a6b275f01
- stable/c/869c6ee62ab8f01bf2419e45326642be5c9b670a
- stable/c/ef44274dae9b0a90d1a97ce8b242a3b8243a7745
- stable/c/496b2ab0fd10f205e08909a125485fdc98843dbe
- stable/c/ced98072d3511b232ae1d3347945f35f30c0e303
- stable/c/38b2d5a57d125e1c17661b8308c0240c4a43b534
- stable/c/4cb9807c9b53bf1e5560420d26f319f528b50268
- stable/c/08d1914293dae38350b8088980e59fbc699a72fe