btrfs: send: check for inline extents in range_is_hole_in_parent()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 82bfb2e7b645c8f228dc3b6d3b27b0b10125ca4f · < 08b096c1372cd69627f4f559fb47c9fb67a52b39| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: send: check for inline extents in range_is_hole_in_parent()
Before accessing the disk_bytenr field of a file extent item we need to check if we are dealing with an inline extent. This is because for inline extents their data starts at the offset of the disk_bytenr field. So accessing the disk_bytenr means we are accessing inline data or in case the inline data is less than 8 bytes we can actually cause an invalid memory access if this inline extent item is the first item in the leaf or access metadata from other items.
From the CVE record · Linux
The btrfs send code can read inline extent data as a disk address without first checking the extent type. If the inline data is less than 8 bytes, this can cause an invalid memory access; the input does not specify attacker access requirements or whether user interaction is needed.
Engineers running the Linux kernel with btrfs should check their kernel version; affected versions are not specified.