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 injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange.
Does this matter?
Lower severity and a low EPSS score (0.27%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.27% probability · 19th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-416
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932Patch
- https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5Patch
- https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5bPatch
- https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932Patch
- https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5Patch
- https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5bPatch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.