Affects core Linux kernel/XFS; widely deployed infrastructure with potential data loss; high severity.
CVE-2026-43187
Linux kernel XFS freemap underflow may cause data loss on setxattr.
Is CVE-2026-43187 being exploited?
Not confirmed. CVE-2026-43187 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-43187?
CVE-2026-43187 is rated High with a CVSS score of 8.8. 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-43187?
Yes. A fix has been recorded for CVE-2026-43187. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43187 affect?
CVE-2026-43187 affects Linux kernel, XFS filesystem. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43187?
Apply kernel update with XFS freemap fix
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker could trigger freemap mismanagement, causing data loss/corruption during setxattr.
Patch when possible
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f3c0d1fc1eadbb4adbee5ab7757d41d35f48325b
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < aa9083d97e2157da3c6fb45ddb1a97af7f188f7f
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a631899025d47ea1aa6464d76db5b4d3b6d196fd
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < ffaf5c99d0f862db021fb1af8b813c1416b1beb2
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e1b8c6452ee99a30e188a88f3f3f804fb1c6004a
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f31a8334e1c54b126fcecf98645a49b6bc5ad399
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 479b05fc3ee272090f671b06a41f3da8aa78eece
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 6f13c1d2a6271c2e73226864a0e83de2770b6f34
- affected2.6.12
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.