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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
cdd1fedf8261cd7a73c0596298902ff4f0f04492 to < 0df50d47d17401f9f140dfbe752a65e5d72f9932affectedcdd1fedf8261cd7a73c0596298902ff4f0f04492 to < ff8de2cec65a8c8521faade12a31b39c80e49f5baffectedcdd1fedf8261cd7a73c0596298902ff4f0f04492 to < dc09ef3562726cd520c8338c1640872a60187af5affected
Linux Linux
Default version status: affected
4.7affected0 to < 4.7unaffected5.10.43 to ≤ 5.10.*unaffected5.12.10 to ≤ 5.12.*unaffected5.13 to ≤ *unaffected