btrfs: free mapping node on duplicate reloc root insert
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 57a304cfd43b2b4a5b44b8f5dc026abb34183068 · < ae0629ff9ccb836416ada129f4edc7efea6eaaad| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: free mapping node on duplicate reloc root insert
__add_reloc_root() allocates a mapping_node before inserting it into rc->reloc_root_tree. If rb_simple_insert() finds an existing entry, it returns the existing rb_node and leaves the newly allocated node unlinked.
The error path then returns -EEXIST without freeing the new node. Since the node was never inserted into reloc_root_tree, the later cleanup in put_reloc_control() cannot find it either.
Free the newly allocated node before returning -EEXIST.
The callers currently assert that -EEXIST should not happen, so this is a defensive cleanup for an unexpected duplicate insert path. If the path is ever reached, the local allocation should still be released.
From the CVE record · Linux
The Linux kernel's btrfs code does not free a newly allocated mapping node if an unexpected duplicate relocation root insert occurs. This can leak memory if that path is reached; the input does not describe an attacker-controlled trigger or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with btrfs should check their versions against the vendor advisory; affected versions are not specified.