CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()
Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcommsockalloc()
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56604?
CVE-2024-56604 is classified as a high severity vulnerability in the Linux kernel affecting Bluetooth functionality.
How do I fix CVE-2024-56604?
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.
Which Linux kernel versions are vulnerable to CVE-2024-56604?
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.
What component of the Linux kernel does CVE-2024-56604 affect?
CVE-2024-56604 affects the Bluetooth RFCOMM implementation in the Linux kernel.
Are all Linux distributions affected by CVE-2024-56604?
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.