PatchSiren cyber security CVE debrief
CVE-2026-43118 Linux CVE debrief
A Linux kernel vulnerability has been identified and resolved, concerning the handling of inode sizes during log replay in the btrfs filesystem. This issue could lead to file size inconsistencies after a power failure. The vulnerability arises from the logging mechanism in the btrfs filesystem, which sometimes fails to update inode sizes correctly during log replay, potentially resulting in file size discrepancies. Linux kernel maintainers, Linux distribution maintainers, system administrators, and users of Linux systems utilizing the btrfs filesystem should assess their exposure and apply patches or mitigations as necessary. The fix involves ensuring that the real generation of an
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-06
- Original CVE updated
- 2026-10-21
- Advisory published
- 2026-05-06
- Advisory updated
- 2026-10-21
Who should care
Linux kernel maintainers, Linux distribution maintainers, system administrators, and users of Linux systems utilizing the btrfs filesystem should assess their exposure and apply patches or mitigations as necessary.
Why it matters
CVE-2026-43118 is a medium-severity vulnerability in the Linux kernel's btrfs filesystem. It affects inode size handling during log replay, potentially leading to file size inconsistencies. Linux kernel maintainers, distribution maintainers, system administrators, and users of btrfs filesystems should assess exposure and apply patches.
- Inconsistent file sizes may occur after power failure, potentially affecting data integrity.
- System administrators may need to verify and correct file sizes manually.
- Applying patches may require system downtime or reboot.
- Further investigation may be needed to determine the full scope of affected systems and files.
Technical summary
The Linux kernel vulnerability concerns the btrfs filesystem's handling of inode sizes during log replay. When logging inode existence, the generation of the logged inode item is set to 0, which can lead to incorrect inode size preservation. This issue can cause file size inconsistencies after a power failure. The fix involves ensuring that the real generation of the inode is logged if it was logged in the current transaction with the i_size previously logged.
Defensive priority
Medium priority for Linux kernel maintainers and users, especially those utilizing btrfs filesystems, to apply patches and ensure system stability.
Recommended defensive actions
- Apply patches provided by the Linux kernel maintainers to ensure system stability.
- Review and update Linux kernel versions to versions that include the fix.
- Monitor system logs for potential issues related to btrfs filesystem operations.
- Perform a thorough review of system configurations and apply necessary patches.
- Verify the integrity of affected systems and ensure data consistency.
- Implement compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions and retest remediated assets to ensure resolution.
Evidence notes
The CVE record and associated source references provide details on the vulnerability, including its description, affected versions, and patches. However, specific exploitation details or victim information are not provided.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-43118 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-43118
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-43118 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-43118
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/03e966b63df5b06790310c1faaf3e0cb43adea8b
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/5254d4181add9dfaa5e3519edd71cc8f752b2f85
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/91990732ec4ce5c09361d498c6d621f5a76ee1f2
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c939bfa67d221f75351a5bf2fc912e8125547b7e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/fddb157536e67a055597f00a8b4922d5f5ed0826
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.