btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST
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 |
6.8
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST
At the end of btrfs_load_block_group_zone_info() the first thing we do is to ensure that if the mapping type is not a SINGLE one and there is no RAID stripe tree, then we return early with an error.
Doing that, though, prevents the code from running the last calls from this function which are about freeing memory allocated during its run. Hence, in this case, instead of returning early, we set the ret value and fall through the rest of the cleanup code.
From the CVE record · Linux
The Linux kernel's btrfs code can leak memory when it rejects a non-SINGLE data profile without a RAID stripe tree. The description does not specify an attacker action or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with btrfs should check their versions; affected versions are not specified.