btrfs: fix inode list leak during backref walking at resolve_indirect_refs()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3301958b7c1dae8f0f5ded63aa881e0b71e78464 · < 396515db923ad5cbeb179d6b88927870b4cbebb7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix inode list leak during backref walking at resolve_indirect_refs()
During backref walking, at resolve_indirect_refs(), if we get an error we jump to the 'out' label and call ulist_free() on the 'parents' ulist, which frees all the elements in the ulist - however that does not free any inode lists that may be attached to elements, through the 'aux' field of a ulist node, so we end up leaking lists if we have any attached to the unodes.
Fix this by calling free_leaf_list() instead of ulist_free() when we exit from resolve_indirect_refs(). The static function free_leaf_list() is moved up for this to be possible and it's slightly simplified by removing unnecessary code.
From the CVE record · Linux
The Linux kernel's btrfs code can leak inode lists when resolve_indirect_refs() encounters an error during backref walking. The input does not specify how an attacker could trigger the error or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with btrfs should check their kernel vendor's advisory for affected versions; none are specified in the input.