btrfs: fix uninitialized pointer free in add_inode_ref()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
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.
From the CVE record · Linux
The Linux kernel's btrfs add_inode_ref() function can free an uninitialized pointer if read_one_inode() returns NULL. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with btrfs should check their versions; affected versions are not specified.