Vulnerability · Published Jan 13, 2026 · Assigned by Linux

CVE-2025-68778btrfs: don't log conflicting inode if it's a dir moved in the current transaction

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 89.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current transaction, as this can result an attempt to have a directory with two hard links during log replay, one for the old parent directory and another for the new parent directory. The following scenario triggers that issue: 1) We have directories "dir1" and "dir2" created in a past transaction. Directory "dir1" has inode A as its parent directory; 2) We move "dir1" to some other directory; 3) We create a file with the name "dir1" in directory inode A; 4) We fsync the new file. This results in logging the inode of the new file and the inode for the directory "dir1" that was previously moved in the current transaction. So the log tree has the INODE_REF item for the new location of "dir1"; 5) We move the new file to some other directory. This results in updating the log tree to included the new INODE_REF for the new location of the file and removes the INODE_REF for the old location. This happens during the rename when we call btrfs_log_new_name(); 6) We fsync the file, and that persists the log tree changes done in the previous step (btrfs_log_new_name() only updates the log tree in memory); 7) We have a power failure; 8) Next time the fs is mounted, log replay happens and when processing the inode for directory "dir1" we find a new INODE_REF and add that link, but we don't remove the old link of the inode since we have not logged the old parent directory of the directory inode "dir1". As a result after log replay finishes when we trigger writeback of the subvolume tree's extent buffers, the tree check will detect that we have a directory a hard link count of 2 and we get a mount failure. The errors and stack traces reported in dmesg/syslog are like this: [ 3845.729764] BTRFS info (device dm-0): start tree-log replay [ 3845.730304] page: refcount:3 mapcount:0 mapping:000000005c8a3027 index:0x1d00 pfn:0x11510c [ 3845.731236] memcg:ffff9264c02f4e00 [ 3845.731751] aops:btree_aops [btrfs] ino:1 [ 3845.732300] flags: 0x17fffc00000400a(uptodate|private|writeback|node=0|zone=2|lastcpupid=0x1ffff) [ 3845.733346] raw: 017fffc00000400a 0000000000000000 dead000000000122 ffff9264d978aea8 [ 3845.734265] raw: 0000000000001d00 ffff92650e6d4738 00000003ffffffff ffff9264c02f4e00 [ 3845.735305] page dumped because: eb page dump [ 3845.735981] BTRFS critical (device dm-0): corrupt leaf: root=5 block=30408704 slot=6 ino=257, invalid nlink: has 2 expect no more than 1 for dir [ 3845.737786] BTRFS info (device dm-0): leaf 30408704 gen 10 total ptrs 17 free space 14881 owner 5 [ 3845.737789] BTRFS info (device dm-0): refs 4 lock_owner 0 current 30701 [ 3845.737792] item 0 key (256 INODE_ITEM 0) itemoff 16123 itemsize 160 [ 3845.737794] inode generation 3 transid 9 size 16 nbytes 16384 [ 3845.737795] block group 0 mode 40755 links 1 uid 0 gid 0 [ 3845.737797] rdev 0 sequence 2 flags 0x0 [ 3845.737798] atime 1764259517.0 [ 3845.737800] ctime 1764259517.572889464 [ 3845.737801] mtime 1764259517.572889464 [ 3845.737802] otime 1764259517.0 [ 3845.737803] item 1 key (256 INODE_REF 256) itemoff 16111 itemsize 12 [ 3845.737805] index 0 name_len 2 [ 3845.737807] item 2 key (256 DIR_ITEM 2363071922) itemoff 16077 itemsize 34 [ 3845.737808] location key (257 1 0) type 2 [ 3845.737810] transid 9 data_len 0 name_len 4 [ 3845.737811] item 3 key (256 DIR_ITEM 2676584006) itemoff 16043 itemsize 34 [ 3845.737813] location key (258 1 0) type 2 [ 3845.737814] transid 9 data_len 0 name_len 4 [ 3845.737815] item 4 key (256 DIR_INDEX 2) itemoff 16009 itemsize 34 [ 3845.737816] location key (257 1 0) type 2 [ ---truncated---

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.162-1DEBIAN-CVE-2025-68778
Debian:13linux6.12.69-1DSA-6126-1
Debian:13linux6.12.69-1DEBIAN-CVE-2025-68778
Debian:14linux6.18.3-1DEBIAN-CVE-2025-68778
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux6.8.0-110.110UBUNTU-CVE-2025-68778
Ubuntu:25.10linux6.17.0-22.22USN-8177-1
Ubuntu:25.10linux6.17.0-22.22UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-aws6.8.0-1052.55UBUNTU-CVE-2025-68778
Ubuntu:25.10linux-aws6.17.0-1012.12USN-8183-2
Ubuntu:25.10linux-aws6.17.0-1012.12UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1USN-8183-2
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure6.8.0-1054.60UBUNTU-CVE-2025-68778
Ubuntu:25.10linux-azure6.17.0-1013.13USN-8245-1
Ubuntu:25.10linux-azure6.17.0-1013.13UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1USN-8245-1
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1058.65UBUNTU-CVE-2025-68778
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-gcp6.8.0-1054.57UBUNTU-CVE-2025-68778
Ubuntu:25.10linux-gcp6.17.0-1012.12USN-8183-1
Ubuntu:25.10linux-gcp6.17.0-1012.12UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1USN-8183-1
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-gke6.8.0-1050.56UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1037.40UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1UBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-ibm6.8.0-1051.51UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1051.51~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-110.110.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-110.110.1~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1051.54UBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1051.54~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1051.54.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1022.22UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20UBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20USN-8245-1
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oracle6.8.0-1049.50UBUNTU-CVE-2025-68778
Ubuntu:25.10linux-oracle6.17.0-1011.11UBUNTU-CVE-2025-68778
Ubuntu:25.10linux-oracle6.17.0-1011.11USN-8183-2
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1UBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1049.50~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-raspi6.8.0-1052.56UBUNTU-CVE-2025-68778
Ubuntu:25.10linux-raspi6.17.0-1013.13UBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68778
Ubuntu:25.10linux-realtime6.17.0-1010.11USN-8177-1
Ubuntu:25.10linux-realtime6.17.0-1010.11UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68778
Ubuntu:25.10linux-riscv6.17.0-22.22.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-riscv-6.176.17.0-22.22.1~24.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-68778
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1028.29UBUNTU-CVE-2025-68778
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2025-68778

Affected products (as reported)

VendorProductVersions
Linux Linux 44f714dae50a2e795d3268a6831762aa6fa54f55 – before d64f3834dffef80f0a9185a037617a54ed7f4bd244f714dae50a2e795d3268a6831762aa6fa54f55 – before 7359e1d39c78816ecbdb0cb4e93975794ce5397344f714dae50a2e795d3268a6831762aa6fa54f55 – before d478f50727c3ee46d0359f0d2ae114f70191816e44f714dae50a2e795d3268a6831762aa6fa54f55 – before a35788ddf8df65837897ecbb0ddb2896b863159e44f714dae50a2e795d3268a6831762aa6fa54f55 – before 266273eaf4d99475f1ae57f687b3e42bc71ec6f0
Linux Linux 4.8

References