CVE-2024-50087

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).

Weakness

The product accesses or uses a pointer that has not been initialized.

Affected Software

Extended Description

If the pointer contains an uninitialized value, then the value might not point to a valid memory location. This could cause the product to read from or write to unexpected memory locations, leading to a denial of service. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked. If an attacker can influence the portion of uninitialized memory that is contained in the pointer, this weakness could be leveraged to execute code or perform other attacks. Depending on memory layout, associated memory management behaviors, and product operation, the attacker might be able to influence the contents of the uninitialized pointer, thus gaining more fine-grained control of the memory location to be accessed.

References

• 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