CVE-2024-56604

published 27 Dec 2024 · updated 4 Oct 2026

Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 32df687e129ef0f9afcbcc914f7c32deb28fd481, Kernel 3945c799f12b8d1f49a3b48369ca494d981ac465, Kernel 6021ccc2471b7b95e29b7cfc7938e042bf56e281 and 1 more.

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().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <32df687e129ef0f9afcbcc914f7c32deb28fd481, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3945c799f12b8d1f49a3b48369ca494d981ac465, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6021ccc2471b7b95e29b7cfc7938e042bf56e281, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ac3eaac4cf142a15fe67be747a682b1416efeb6e32df687e129ef0f9afcbcc914f7c32deb28fd481, 3945c799f12b8d1f49a3b48369ca494d981ac465, 6021ccc2471b7b95e29b7cfc7938e042bf56e281, ac3eaac4cf142a15fe67be747a682b1416efeb6e

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-56604 severity on Zeptric[![CVE-2024-56604](https://zeptric.io/badge/cve/CVE-2024-56604.svg)](https://zeptric.io/cve/CVE-2024-56604)