CVE-2025-71183

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

btrfs: always detect conflicting inodes when logging inode refs

After rename exchanging (either with the rename exchange operation or

regular renames in multiple non-atomic steps) two inodes and at least

one of them is a directory, we can end up with a log tree that contains

only of the inodes and after a power failure that can result in an attempt

to delete the other inode when it should not because it was not deleted

before the power failure. In some case that delete attempt fails when

the target inode is a directory that contains a subvolume inside it, since

the log replay code is not prepared to deal with directory entries that

point to root items (only inode items).

1) We have directories "dir1" (inode A) and "dir2" (inode B) under the

same parent directory;

2) We have a file (inode C) under directory "dir1" (inode A);

3) We have a subvolume inside directory "dir2" (inode B);

4) All these inodes were pers

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References