First published: Fri Dec 27 2024(Updated: )
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().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <6.1.120 | |
Linux Kernel | >=6.2<6.6.66 | |
Linux Kernel | >=6.7<6.12.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-56604 is classified as a high severity vulnerability in the Linux kernel affecting Bluetooth functionality.
To fix CVE-2024-56604, upgrade your Linux kernel to a version that is equal to or greater than 6.1.120 or within the safe ranges not affected by this CVE.
Linux kernel versions before 6.1.120, between 6.2 and 6.6.66, and between 6.7 and 6.12.5 are vulnerable to CVE-2024-56604.
CVE-2024-56604 affects the Bluetooth RFCOMM implementation in the Linux kernel.
Not all Linux distributions will be affected; it depends on whether they use versions of the Linux kernel that are vulnerable to CVE-2024-56604.