CVE-2024-56604 - CVE House
Back to Database
Status published Unknown CVE-2024-56604

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

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

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2024-56604

Credits & Attribution

No credits recorded in the NVD database.

References

More from Linux

View All →
CVE-2025-71315
drm/vkms: Convert to DRM's vblank timer
Unknown 0
CVE-2025-71314
drm/panthor: Recover from panthor_gpu_flush_caches() failures
Unknown 0
CVE-2025-71313
PCI: endpoint: Add missing NULL check for alloc_workqueue()
Unknown 0
CVE-2025-71312
fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()
Unknown 0
CVE-2025-71311
fs/ntfs3: Initialize new folios before use
Unknown 0

Affected Vendor

Affected Software

Linux
Vulnerable Versions:
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 2.6.12, 0, 6.1.120, 6.6.66, 6.12.5, 6.13

Timeline

Official Publish: December 27th, 2024
Last Modified: May 11th, 2026
Added to House: July 22nd, 2026

CVSS Vectors

No vector data available

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.