CVE-2024-50087: btrfs: fix uninitialized pointer free on read_alloc_one_name() error
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix uninitialized pointer free on readalloconename() error
The function readalloconename() does not initialize the name field of the passed fscryptstr struct if kmalloc fails to allocate the corresponding buffer. Thus, it is not guaranteed that fscryptstr.name is initialized when freeing it.
This is a follow-up to the linked patch that fixes the remaining instances of the bug introduced by commit e43eec81c516 ("btrfs: use struct qstr instead of name and namelen pairs").
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.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-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-50087?
CVE-2024-50087 has a high severity rating due to its potential to cause uninitialized pointer dereference issues.
How do I fix CVE-2024-50087?
To fix CVE-2024-50087, update the Linux kernel to a patched version that addresses this vulnerability.
What versions of the Linux kernel are affected by CVE-2024-50087?
CVE-2024-50087 affects various versions of the Linux kernel between 6.1.57 to 6.1.114, as well as versions up to 6.6.58 and others in the 6.12 release candidates.
What are the potential impacts of CVE-2024-50087?
The impacts of CVE-2024-50087 may include system crashes or unintended behavior due to uninitialized memory access.
Is CVE-2024-50087 being actively exploited?
As of now, there is no public information indicating that CVE-2024-50087 is being actively exploited in the wild.