Affects Linux kernel/XFS, core infrastructure; mis-sized log roundoff can cause data loss and downtime across Linux deployments.
CVE-2026-43365
Linux kernel XFS: log roundoff bug may cause log corruption and unmountable FS on 4k disks.
Is CVE-2026-43365 being exploited?
Not confirmed. CVE-2026-43365 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-43365?
CVE-2026-43365 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-43365?
Yes. A fix has been recorded for CVE-2026-43365. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43365 affect?
CVE-2026-43365 affects Linux kernel (XFS), Servers/desktops with 4k-sector disks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43365?
Update to patched kernel/XFS and verify mounts after deployment
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Can lead to log corruption and failed mounts, risking data loss and downtime on affected systems.
Patch when possible
- affected>= a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 and < 5afae524f83d6a18517298491a5624cb0eae5029
- affected>= a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 and < 2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40
- affected>= a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 and < 41e91dff2d3974730b5ee50daa8e27ec254cbf91
- affected>= a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 and < e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d
- affected>= a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 and < 446a1f5bb64ba38adb93cb043ff0f7b85e8937ca
- affected>= a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 and < 5e7148402dfc4a5b7894d8e97b15e5c2e70924aa
- affected>= a6a65fef5ef8d0a6a0ce514eb66b2f3dfa777b48 and < 52a8a1ba883defbfe3200baa22cf4cd21985d51a
- affected5.14
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.