CVE-2024-50044 Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change
A deadlock in the Linux kernel Bluetooth RFCOMM module allows local attackers to cause a system denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-50044?
CVE-2024-50044 is a low-severity vulnerability in Linux kernel, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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
Weakness: CWE-667
Which versions are affected by CVE-2024-50044?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2024-50044?
Apply the vendor's patch.
Is CVE-2024-50044 being exploited?
There is no known exploitation of CVE-2024-50044 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as AZL-51123, AZL-51279, BELL-CVE-2024-50044, DEBIAN-CVE-2024-50044, GHSA-qjvc-xmqv-cwr9, UBUNTU-CVE-2024-50044.