5.5

CVE-2026-43118: btrfs: fix zero size inode with non-zero size after log replay

Modified
AliasesUBUNTU-CVE-2026-43118DEBIAN-CVE-2026-43118CGA-2h6h-4h4q-w5fg
Published 06-05-2026Last modified 30-10-2026

Vulnerability summary

CVE-2026-43118 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.16% chance of exploitation in the next 30 days, higher than 4.8% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.16%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 18 · Related 16

Timeline

  1. 06-05-2026
    PublishedVulnerability first disclosed.
  2. 30-10-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix zero size inode with non-zero size after log replay When logging that an inode exists, as part of logging a new name or logging new dir entries for a directory, we always set the generation of the logged inode item to 0. This is to signal during log replay (in overwrite_item()), that we should not set the i_size since we only logged that an inode exists, so the i_size of the inode in the subvolume tree must be preserved (as when we log new names or that an inode exists, we don't log extents). This works fine except when we have already logged an inode in full mode or it's the first time we are logging an inode created in a past transaction, that inode has a new i_size of 0 and then we log a new name for the inode (due to a new hardlink or a rename), in which case we log an i_size of 0 for the inode and a generation of 0, which causes the log replay code to not update the inode's i_size to 0 (in overwrite_item()). An example scenario: mkdir /mnt/dir xfs_io -f -c "pwrite 0 64K" /mnt/dir/foo sync xfs_io -c "truncate 0" -c "fsync" /mnt/dir/foo ln /mnt/dir/foo /mnt/dir/bar xfs_io -c "fsync" /mnt/dir <power fail> After log replay the file remains with a size of 64K. This is because when we first log the inode, when we fsync file foo, we log its current i_size of 0, and then when we create a hard link we log again the inode in exists mode (LOG_INODE_EXISTS) but we set a generation of 0 for the inode item we add to the log tree, so during log replay overwrite_item() sees that the generation is 0 and i_size is 0 so we skip updating the inode's i_size from 64K to 0. Fix this by making sure at fill_inode_item() we always log the real generation of the inode if it was logged in the current transaction with the i_size we logged before. Also if an inode created in a previous transaction is logged in exists mode only, make sure we log the i_size stored in the inode item located from the commit root, so that if we log multiple times that the inode exists we get the correct i_size. A test case for fstests will follow soon.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.16%

Chance of exploitation in the next 30 days

Percentile

5%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.16% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu159 products
  • linuxAll versions (No fix recorded) | < 6.8.0-151.151
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1070.76
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard11 products
  • linux-aws-6.12< 6.12.85-r2
  • linux-aws-6.18< 6.18.31-r0
  • linux-azure-6.12< 6.12.85-r2
  • linux-azure-6.18< 6.18.24-r1
  • linux-gcp-6.12< 6.12.85-r2
Debian2 products
  • linuxAll versions (No fix recorded) | < 6.1.192-1 | < 6.12.115-2 | < 6.19.14-1
  • linux-6.12< 6.12.115-2~deb12u1
Linux2 products
  • linux≥ 12fcfd22fe5bf4fe74710232098bc101af497995, < 126999610eddeb1de3b47680585f4bc9531dc7f4 | ≥ 12fcfd22fe5bf4fe74710232098bc101af497995, < c939bfa67d221f75351a5bf2fc912e8125547b7e | ≥ 12fcfd22fe5bf4fe74710232098bc101af497995, < 91990732ec4ce5c09361d498c6d621f5a76ee1f2 | ≥ 12fcfd22fe5bf4fe74710232098bc101af497995, < fddb157536e67a055597f00a8b4922d5f5ed0826 | ≥ 12fcfd22fe5bf4fe74710232098bc101af497995, < 03e966b63df5b06790310c1faaf3e0cb43adea8b | ≥ 12fcfd22fe5bf4fe74710232098bc101af497995, < 5254d4181add9dfaa5e3519edd71cc8f752b2f85 | 2.6.30
  • linux_kernel≥ 2.6.30, < 6.18.24 | ≥ 6.19, < 6.19.14 | 7.0:rc1 | 7.0:rc2 | 7.0:rc3 | 7.0:rc4 | 7.0:rc5

4 vendors · 174 products

References

13 links
Show all 13 references