Linux kernel XFS undersized l_iclog_roundoff log corruption vulnerability
CVE-2026-43365 is a vulnerability in the Linux kernel's XFS filesystem code caused by incorrect handling of the in-core log roundoff value (l_iclog_roundoff). When the XFS superblock does not specify a log stripe unit, the kernel can set the roundoff value to 512 bytes even when the log sector size is 4096 bytes. On affected filesystems, particularly those using 4K physical sectors, this mismatch can result in torn-write CRC failures, corrupted XFS journal/log state, and subsequent log recovery or mount failures. The issue is described by the upstream fix as "xfs: fix undersized l_iclog_roundoff values." The provided diagnostic output shows CRC failure detection in the log, inability to locate the log tail, and log mount/recovery failure with error -74. The content also notes that malformed filesystems can be produced by a broken mkfs in current xfsprogs for-next, and that a fuzzed on-disk superblock can also trigger the unsafe condition.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.