Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix abort logic in btrfs_replace_file_extents Error injection testing uncovered a case where we'd end up with a corrupt file system with a missing extent in the middle of a file. This occurs because the if statement to decide if we should abort is wrong. The only way we would abort in this case is if we got a ret != -EOPNOTSUPP and we called from the file clone code. However the prealloc code uses this path too. Instead we need to abort if there is an error, and the only error we _don't_ abort on is -EOPNOTSUPP and only if we came from the clone file code.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
8fccebfa534c7984864394fa03608305e4929aae to < 0e32a2b85c7d92ece86c17dfef390c5ed79c6378affected8fccebfa534c7984864394fa03608305e4929aae to < 0e309e1152fc34ef75991d9d69b165dbf75bf26caffected8fccebfa534c7984864394fa03608305e4929aae to < 4afb912f439c4bc4e6a4f3e7547f2e69e354108faffected
Linux Linux
Default version status: affected
5.10affected0 to < 5.10unaffected5.10.75 to ≤ 5.10.*unaffected5.14.14 to ≤ 5.14.*unaffected5.15 to ≤ *unaffected