CVE-2024-50044: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: FIX possible deadlock in rfcommskstatechange
rfcommskstatechange attempts to use socklock so it must never be called with it locked but rfcommsockioctl 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 (sklock-AFBLUETOOTH-BTPROTORFCOMM){+.+.}-{0:0}, at: locksock include/net/sock.h:1671 [inline] ffff88807c396258 (sklock-AFBLUETOOTH-BTPROTORFCOMM){+.+.}-{0:0}, at: rfcommskstatechange+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73
but task is already holding lock: ffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: rfcommdlcclose+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491
Other sources
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: FIX possible deadlock in rfcommskstatechange
rfcommskstatechange attempts to use socklock so it must never be called with it locked but rfcommsockioctl 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 (sklock-AFBLUETOOTH-BTPROTORFCOMM){+.+.}-{0:0}, at: locksock include/net/sock.h:1671 [inline] ffff88807c396258 (sklock-AFBLUETOOTH-BTPROTORFCOMM){+.+.}-{0:0}, at: rfcommskstatechange+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73
but task is already holding lock: ffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: rfcommdlcclose+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491
— NVD
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50044?
CVE-2024-50044 has not been explicitly assigned a severity rating, but it relates to a potential deadlock issue in the Bluetooth RFCOMM module of the Linux kernel.
How do I fix CVE-2024-50044?
To fix CVE-2024-50044, update the Linux kernel to versions that address the vulnerability, such as 5.10.227, 5.15.168, 6.1.113, or later.
What versions of the Linux kernel are affected by CVE-2024-50044?
CVE-2024-50044 affects multiple versions of the Linux kernel between 2.6.27 and 6.12-rc2, specifically those within certain version ranges.
What components are involved in CVE-2024-50044?
CVE-2024-50044 involves the rfcomm_sk_state_change function in the Bluetooth RFCOMM implementation of the Linux kernel.
Which distributions might be vulnerable to CVE-2024-50044?
Distributions running affected versions of the Linux kernel, such as Debian, may be vulnerable to CVE-2024-50044.