CVE-2024-50024: net: Fix an unsafe loop on the list
In the Linux kernel, the following vulnerability has been resolved:
net: Fix an unsafe loop on the list
The kernel may crash when deleting a genetlink family if there are still listeners for that family:
Oops: Kernel access of bad area, sig: 11 [#1] ... NIP [c000000000c080bc] netlinkupdatesocketmc+0x3c/0xc0 LR [c000000000c0f764] netlinkclearmulticastusers+0x74/0xc0 Call Trace: netlinkclearmulticastusers+0x74/0xc0 genlunregisterfamily+0xd4/0x2d0
Change the unsafe loop on the list to a safe one, because inside the loop there is an element removal from this list.
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 5.10.234-1Fixed 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-50024?
CVE-2024-50024 has been classified as having a high severity due to the potential for kernel crashes.
How do I fix CVE-2024-50024?
To fix CVE-2024-50024, update the Linux kernel to a version that includes the patch, specifically versions 6.1.123-1, 6.12.12-1, or later.
Which versions of Linux kernel are affected by CVE-2024-50024?
CVE-2024-50024 affects Linux kernel versions from 2.6.32 up to 6.11.4, excluding patched versions.
What systems are impacted by CVE-2024-50024?
Systems running vulnerable versions of the Linux kernel, particularly those using the genetlink family, are impacted by CVE-2024-50024.
Is there a known exploit for CVE-2024-50024?
As of now, there is no publicly available exploit for CVE-2024-50024, but it presents a significant risk due to its potential to crash the kernel.