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

Mon, 04 Nov 2024 13: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-03-15T20:14:21.300Z

Updated: 2024-11-04T11:59:39.913Z

Reserved: 2024-03-04T18:12:48.836Z

Link: CVE-2021-47113

cve-icon Vulnrichment

Updated: 2024-08-04T05:24:39.855Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-03-15T21:15:06.673

Modified: 2024-03-17T22:38:29.433

Link: CVE-2021-47113

cve-icon Redhat

Severity : Low

Publid Date: 2024-03-15T00:00:00Z

Links: CVE-2021-47113 - Bugzilla