CVE-2021-47433
published 2024-05-22CVE-2021-47433: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix abort logic in btrfs_replace_file_extents Error injection testing uncovered a…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.57%
44.2th percentile
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
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.16-1 (bookworm) | linux 5.14.16-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8fccebfa534c7984864394fa03608305e4929aae < 0e32a2b85c7d92ece86c17dfef390c5ed79c6378 | 0e32a2b85c7d92ece86c17dfef390c5ed79c6378 |
| linux | linux | >= 8fccebfa534c7984864394fa03608305e4929aae < 0e309e1152fc34ef75991d9d69b165dbf75bf26c | 0e309e1152fc34ef75991d9d69b165dbf75bf26c |
| linux | linux | >= 8fccebfa534c7984864394fa03608305e4929aae < 4afb912f439c4bc4e6a4f3e7547f2e69e354108f | 4afb912f439c4bc4e6a4f3e7547f2e69e354108f |
| linux | linux_kernel | < 5.10.75 | 5.10.75 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.84-1 | 5.10.84-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 5.11 < 5.14.14 | 5.14.14 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: btrfs: fix abort logic in btrfs_replace_file_extents
vendor_redhat·2024-05-22·CVSS 5.5
CVE-2021-47433 [MEDIUM] CWE-754 kernel: btrfs: fix abort logic in btrfs_replace_file_extents
kernel: btrfs: fix abort logic in btrfs_replace_file_extents
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.
A vulnerability was found in the btrfs file system's `btrfs_replace_file_extents` function within t
Debian
CVE-2021-47433: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: fix ...
vendor_debian·2021·CVSS 5.5
CVE-2021-47433 [MEDIUM] CVE-2021-47433: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: fix ...
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.
Scope: local
bookworm: resolved (fixed in 5.14.16-1)
bullseye: resolved (fixed in 5.10.84-1)
forky: resolved (fixed in 5.14.16-1)
sid: resolved (fixed in 5.14.16-
GHSA
GHSA-6x3x-fg57-3vcm: In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix abort logic in btrfs_replace_file_extents
Error injection testing unc
ghsa_unreviewed·2024-05-22
CVE-2021-47433 [MEDIUM] GHSA-6x3x-fg57-3vcm: In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix abort logic in btrfs_replace_file_extents
Error injection testing unc
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.
OSV
CVE-2021-47433: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix abort logic in btrfs_replace_file_extents Error injection testing uncov
osv·2024-05-22·CVSS 5.5
CVE-2021-47433 [MEDIUM] CVE-2021-47433: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix abort logic in btrfs_replace_file_extents Error injection testing uncov
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0e309e1152fc34ef75991d9d69b165dbf75bf26chttps://git.kernel.org/stable/c/0e32a2b85c7d92ece86c17dfef390c5ed79c6378https://git.kernel.org/stable/c/4afb912f439c4bc4e6a4f3e7547f2e69e354108fhttps://git.kernel.org/stable/c/0e309e1152fc34ef75991d9d69b165dbf75bf26chttps://git.kernel.org/stable/c/0e32a2b85c7d92ece86c17dfef390c5ed79c6378https://git.kernel.org/stable/c/4afb912f439c4bc4e6a4f3e7547f2e69e354108f
2024-05-22
Published