File-size corruption via stale inode log replay
Published May 6, 2026 · Updated May 6, 2026
Incorrect btrfs log replay in Linux Kernel allows local users to retain stale file sizes after a crash or power failure. The overwrite_item() path treats generation zero as an instruction to preserve i_size, so a later LOG_INODE_EXISTS record can suppress a previously logged truncation to zero. The sequence requires write access to a btrfs filesystem, a truncate followed by a hard link and fsync, and subsequent log replay; the result is stale inode size metadata rather than code execution.
Summary
What happened
Incorrect btrfs log replay in Linux Kernel allows local users to retain stale file sizes after a crash or power failure. The overwrite_item() path treats generation zero as an instruction to preserve i_size, so a later LOG_INODE_EXISTS record can suppress a previously logged truncation to zero. The sequence requires write access to a btrfs filesystem, a truncate followed by a hard link and fsync, and subsequent log replay; the result is stale inode size metadata rather than code execution.
The record
- CVE
- CVE-2026-43118
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <03e966b63df5b06790310c1faaf3e0cb43adea8b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5254d4181add9dfaa5e3519edd71cc8f752b2f85
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fddb157536e67a055597f00a8b4922d5f5ed0826
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo