CVE-2021-47113
published 2024-03-15CVE-2021-47113: In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.27%
18.8th percentile
In the Linux kernel, the following vulnerability has been resolved:
btrfs: abort in rename_exchange if we fail to insert the second ref
Error injection stress uncovered a problem where we'd leave a dangling
inode ref if we failed during a rename_exchange. This happens because
we insert the inode ref for one side of the rename, and then for the
other side. If this second inode ref insert fails we'll leave the first
one dangling and leave a corrupt file system behind. Fix this by
aborting if we did the insert for the first inode ref.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.46-1 (bookworm) | linux 5.10.46-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= cdd1fedf8261cd7a73c0596298902ff4f0f04492 < 0df50d47d17401f9f140dfbe752a65e5d72f9932 | 0df50d47d17401f9f140dfbe752a65e5d72f9932 |
| linux | linux | >= cdd1fedf8261cd7a73c0596298902ff4f0f04492 < ff8de2cec65a8c8521faade12a31b39c80e49f5b | ff8de2cec65a8c8521faade12a31b39c80e49f5b |
| linux | linux | >= cdd1fedf8261cd7a73c0596298902ff4f0f04492 < dc09ef3562726cd520c8338c1640872a60187af5 | dc09ef3562726cd520c8338c1640872a60187af5 |
| linux | linux_kernel | < 5.10.43 | 5.10.43 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 5.11 < 5.12.10 | 5.12.10 |
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: abort in rename_exchange if we fail to insert the second ref
vendor_redhat·2024-03-15·CVSS 5.5
CVE-2021-47113 [MEDIUM] CWE-416 kernel: btrfs: abort in rename_exchange if we fail to insert the second ref
kernel: btrfs: abort in rename_exchange if we fail to insert the second ref
In the Linux kernel, the following vulnerability has been resolved:
btrfs: abort in rename_exchange if we fail to insert the second ref
Error injection stress uncovered a problem where we'd leave a dangling
inode ref if we failed during a rename_exchange. This happens because
we insert the inode ref for one side of the rename, and then for the
other side. If this second inode ref insert fails we'll leave the first
one dangling and leave a corrupt file system behind. Fix this by
aborting if we did the insert for the first inode ref.
Package: kernel (Red Hat Enterprise Linux 6) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel-rt (Red Hat Enterprise Linux 7
Debian
CVE-2021-47113: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: abor...
vendor_debian·2021·CVSS 5.5
CVE-2021-47113 [MEDIUM] CVE-2021-47113: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: abor...
In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange. This happens because we insert the inode ref for one side of the rename, and then for the other side. If this second inode ref insert fails we'll leave the first one dangling and leave a corrupt file system behind. Fix this by aborting if we did the insert for the first inode ref.
Scope: local
bookworm: resolved (fixed in 5.10.46-1)
bullseye: resolved (fixed in 5.10.46-1)
forky: resolved (fixed in 5.10.46-1)
sid: resolved (fixed in 5.10.46-1)
trixie: resolved (fixed in 5.10.46-1)
VulDB
Linux Kernel up to 5.10.42/5.12.9 btrfs rename_exchange injection (0df50d47d174/ff8de2cec65a/dc09ef356272)
vuldb·2026-08-04·CVSS 5.5
CVE-2021-47113 [MEDIUM] Linux Kernel up to 5.10.42/5.12.9 btrfs rename_exchange injection (0df50d47d174/ff8de2cec65a/dc09ef356272)
A vulnerability was found in Linux Kernel up to 5.10.42/5.12.9 and classified as problematic. Affected by this issue is the function rename_exchange of the component btrfs. The manipulation results in injection.
This vulnerability is identified as CVE-2021-47113. The attack can only be performed from the local network. There is not any exploit available.
It is suggested to upgrade the affected component.
OSV
CVE-2021-47113: In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injectio
osv·2024-03-15·CVSS 5.5
CVE-2021-47113 [MEDIUM] CVE-2021-47113: In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injectio
In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange. This happens because we insert the inode ref for one side of the rename, and then for the other side. If this second inode ref insert fails we'll leave the first one dangling and leave a corrupt file system behind. Fix this by aborting if we did the insert for the first inode ref.
GHSA
GHSA-g4rp-89x9-87mq: In the Linux kernel, the following vulnerability has been resolved:
btrfs: abort in rename_exchange if we fail to insert the second ref
Error inject
ghsa_unreviewed·2024-03-15
CVE-2021-47113 [MEDIUM] CWE-416 GHSA-g4rp-89x9-87mq: In the Linux kernel, the following vulnerability has been resolved:
btrfs: abort in rename_exchange if we fail to insert the second ref
Error inject
In the Linux kernel, the following vulnerability has been resolved:
btrfs: abort in rename_exchange if we fail to insert the second ref
Error injection stress uncovered a problem where we'd leave a dangling
inode ref if we failed during a rename_exchange. This happens because
we insert the inode ref for one side of the rename, and then for the
other side. If this second inode ref insert fails we'll leave the first
one dangling and leave a corrupt file system behind. Fix this by
aborting if we did the insert for the first inode ref.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5bhttps://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5b
2024-03-15
Published