CVE-2024-10241
Mar, 29/10/2024 – 08:15
CVE-2024-10241
CVE-2024-10241
Mar, 29/10/2024 – 08:15
CVE-2024-10241
CVE-2024-50480
Mar, 29/10/2024 – 08:15
CVE-2024-50480
CVE-2024-50052
Mar, 29/10/2024 – 08:15
CVE-2024-50052
CVE-2024-10312
Mar, 29/10/2024 – 08:15
CVE-2024-10312
CVE-2024-50494
Mar, 29/10/2024 – 08:15
CVE-2024-50494
CVE-2024-50493
Mar, 29/10/2024 – 08:15
CVE-2024-50493
CVE-2024-50484
Mar, 29/10/2024 – 08:15
CVE-2024-50484
CVE-2024-50482
Mar, 29/10/2024 – 08:15
CVE-2024-50482
CVE-2024-50088
Mar, 29/10/2024 – 01:15
CVE-2024-50088
btrfs: fix uninitialized pointer free in add_inode_ref()
The add_inode_ref() function does not initialize the "name" struct when
it is declared. If any of the following calls to "read_one_inode()
returns NULL,
dir = read_one_inode(root, parent_objectid);
if (!dir) {
ret = -ENOENT;
goto out;
}
inode = read_one_inode(root, inode_objectid);
if (!inode) {
ret = -EIO;
goto out;
}
then "name.name" would be freed on "out" before being initialized.
out:
…
kfree(name.name);
This issue was reported by Coverity with CID 1526744.
CVE-2024-50087
Mar, 29/10/2024 – 01:15
CVE-2024-50087
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").