CVE-2026-43118

Name of the Vulnerable Software and Affected Versions Linux kernel (affected versions not specified)

Description An issue exists in the Btrfs file system where an inode may retain a non-zero size after log replay, even if it was truncated to zero. This occurs because when logging that an inode exists (such as during a rename or hardlink creation), the generation of the logged inode item is set to 0. During log replay, the overwrite item() function interprets a generation of 0 as a signal to preserve the existing i size from the subvolume tree. If an inode was previously logged with an i size of 0 in the same transaction, or if it was created in a past transaction, the replay process fails to update the inode size to 0, potentially leaving the file with its previous size after a power failure.

Recommendations At the moment, there is no information about a newer version that contains a fix for this vulnerability.