CVE-2024-56604 Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()
A use-after-free vulnerability in the Linux kernel's Bluetooth RFCOMM implementation allows attackers to potentially execute code or escalate privileges.
- 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-56604?
CVE-2024-56604 is a high-severity use after free vulnerability in Linux kernel, published on 27 Dec 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: 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().
Weakness: CWE-416
Which versions are affected by CVE-2024-56604?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2024-56604?
Apply the vendor's patch.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2024-56604 being exploited?
There is no known exploitation of CVE-2024-56604 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as AZL-55485, AZL-55611, BELL-CVE-2024-56604, DEBIAN-CVE-2024-56604, GHSA-3h24-5m24-pxvw, ROOT-OS-DEBIAN-11-CVE-2024-56604 and 2 more.