CVE-2021-47113

btrfs: abort in rename_exchange if we fail to insert the second ref

State
Published
Severity
7.1 High
Published
Mar 15, 2024
Updated
Aug 5, 2026
Reserved
Mar 4, 2024

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.1 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • cdd1fedf8261cd7a73c0596298902ff4f0f04492 to before 0df50d47d17401f9f140dfbe752a65e5d72f9932Affected
  • cdd1fedf8261cd7a73c0596298902ff4f0f04492 to before ff8de2cec65a8c8521faade12a31b39c80e49f5bAffected
  • cdd1fedf8261cd7a73c0596298902ff4f0f04492 to before dc09ef3562726cd520c8338c1640872a60187af5Affected
LinuxLinux
  • 4.7Affected
  • before 4.7Not affected
  • 5.10.43 through 5.10.*Not affected
  • 5.12.10 through 5.12.*Not affected
  • 5.13 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.