btrfs: fix zero size inode with non-zero size after log replay
CVE-2026-43118 is a vulnerability related to the btrfs filesystem where an inode can have a zero size but a non-zero size after log replay. This issue affects version 3.0 of the Microsoft product referenced. No CVSS score or detailed impact information is provided. There are no known exploits in the wild and no patch or remediation details are available in the provided data.
AI Analysis
Technical Summary
This vulnerability concerns the btrfs filesystem implementation in Microsoft software version 3.0, where after log replay an inode may incorrectly show a zero size while actually having a non-zero size. The provided information does not include technical details on exploitation or impact, nor does it specify a patch or mitigation. The vulnerability is cataloged under CVE-2026-43118 by the Microsoft Security Response Center.
Potential Impact
The impact is not explicitly described in the provided data. The inconsistency in inode size after log replay could potentially affect filesystem integrity or behavior, but no confirmed exploitation or impact details are available.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or workaround information is provided in the available data.
btrfs: fix zero size inode with non-zero size after log replay
Description
CVE-2026-43118 is a vulnerability related to the btrfs filesystem where an inode can have a zero size but a non-zero size after log replay. This issue affects version 3.0 of the Microsoft product referenced. No CVSS score or detailed impact information is provided. There are no known exploits in the wild and no patch or remediation details are available in the provided data.
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability concerns the btrfs filesystem implementation in Microsoft software version 3.0, where after log replay an inode may incorrectly show a zero size while actually having a non-zero size. The provided information does not include technical details on exploitation or impact, nor does it specify a patch or mitigation. The vulnerability is cataloged under CVE-2026-43118 by the Microsoft Security Response Center.
Potential Impact
The impact is not explicitly described in the provided data. The inconsistency in inode size after log replay could potentially affect filesystem integrity or behavior, but no confirmed exploitation or impact details are available.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or workaround information is provided in the available data.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_vex
- Csaf Version
- 2.0
- Publisher
- Microsoft Security Response Center
- Advisory Id
- msrc_CVE-2026-43118
- Cve Count
- 1
- Additional Cves
- []
- Cvss Version
- null
Threat ID: 6a42ed8d27e9c79719960cb5
Added to database: 06/29/2026, 22:11:25 UTC
Last enriched: 06/29/2026, 22:54:40 UTC
Last updated: 07/31/2026, 19:24:50 UTC
Views: 18
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.