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.
History

Mon, 04 Nov 2024 12:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2024-05-22T06:19:30.244Z

Updated: 2024-11-04T12:05:49.359Z

Reserved: 2024-05-21T14:58:30.830Z

Link: CVE-2021-47433

cve-icon Vulnrichment

Updated: 2024-08-04T05:39:59.455Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-05-22T07:15:08.347

Modified: 2024-05-22T12:46:53.887

Link: CVE-2021-47433

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-05-22T00:00:00Z

Links: CVE-2021-47433 - Bugzilla