Access of Uninitialized Pointer Affecting kernel package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL7-KERNEL-8318901
- published 31 Oct 2024
- disclosed 29 Oct 2024
Introduced: 29 Oct 2024
CVE-2024-50087 Open this link in a new tabHow to fix?
There is no fixed version for RHEL:7 kernel.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel package and not the kernel package as distributed by RHEL.
See How to fix? for RHEL:7 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix uninitialized pointer free on read_alloc_one_name() error
The function read_alloc_one_name() does not initialize the name field of the passed fscrypt_str struct if kmalloc fails to allocate the corresponding buffer. Thus, it is not guaranteed that fscrypt_str.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").
References
- https://access.redhat.com/security/cve/CVE-2024-50087
- https://git.kernel.org/stable/c/1ec28de5e476913ae51f909660b4447eddb28838
- https://git.kernel.org/stable/c/2ab5e243c2266c841e0f6904fad1514b18eaf510
- https://git.kernel.org/stable/c/7fc7c47b9ba0cf2d192f2117a64b24881b0b577f
- https://git.kernel.org/stable/c/b37de9491f140a0ff125c27dd1050185c3accbc1