btrfs: fix uninitialized pointer free on read_alloc_one_name() error
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.8epss 0.2%
exploitation probability
0.2%top 88% of all CVEs
observed exploitation
nono source reports it
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").
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/1ec28de5e476913ae51f909660b4447eddb28838https://git.kernel.org/stable/c/2ab5e243c2266c841e0f6904fad1514b18eaf510https://git.kernel.org/stable/c/7fc7c47b9ba0cf2d192f2117a64b24881b0b577fhttps://git.kernel.org/stable/c/b37de9491f140a0ff125c27dd1050185c3accbc1https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html