Low · published October 22, 2024
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
| Product | Versions | Fixed in |
|---|---|---|
| linux/linux_kernel | ≥ 2.6.27, < 5.10.227 | 5.10.227 |
| linux/linux_kernel | ≥ 5.11, < 5.15.168 | 5.15.168 |
| linux/linux_kernel | ≥ 5.16, < 6.1.113 | 6.1.113 |
| linux/linux_kernel | ≥ 6.2, < 6.6.57 | 6.6.57 |
| linux/linux_kernel | ≥ 6.7, < 6.11.4 | 6.11.4 |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |