First published: Fri Dec 27 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() bt_sock_alloc() allocates the sk object and attaches it to the provided sock object. On error l2cap_sock_alloc() frees the sk object, but the dangling pointer is still attached to the sock object, which may create use-after-free in other code.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <5.4.287 | |
Linux Kernel | >=5.5<5.10.231 | |
Linux Kernel | >=5.11<5.15.174 | |
Linux Kernel | >=5.16<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-56605 affects Linux kernel versions prior to 5.4.287 and versions between 5.5 and 5.10.231, 5.11 and 5.15.174, 5.16 and 6.1.120, 6.2 and 6.6.66, and 6.7 and 6.12.5.
CVE-2024-56605 has not been assigned a specific severity score yet, but it is essential to evaluate its impact based on the context of your environment.
To fix CVE-2024-56605, update your Linux kernel to a version that addresses the vulnerability.
CVE-2024-56605 is a vulnerability related to the Bluetooth L2CAP subsystem in the Linux kernel.
CVE-2024-56605 could potentially lead to resource leaks or unstable behavior if not addressed.