CVE-2021-47113

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 Metrics

• v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.02%• Percentile: 5%

Techniques & Countermeasures

• CWE-416•Use After Free

  The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

• linux•linux

  ≥ cdd1fedf8261cd7a73c0596298902ff4f0f04492, < 0df50d47d17401f9f140dfbe752a65e5d72f9932 | ≥ cdd1fedf8261cd7a73c0596298902ff4f0f04492, < ff8de2cec65a8c8521faade12a31b39c80e49f5b | ≥ cdd1fedf8261cd7a73c0596298902ff4f0f04492, < dc09ef3562726cd520c8338c1640872a60187af5 | 4.7

• linux•linux_kernel

  < 5.10.43 | ≥ 5.11, < 5.12.10 | 5.13:rc1 | 5.13:rc2 | 5.13:rc3 | 5.13:rc4

References (3)

• https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932
• https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5b
• https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5