CVE record · CVE-2026-43053

xfs: close crash window in attr dabtree inactivation

No CVSS scoreEPSS 0.0012 · 1st percentile

Published by the CVE Program (CNA: Linux) at 1 May 2026, 14:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
Linux Linux
  • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 190d54d1d42878fce8c735c2d9ac835725694d3a git
  • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 7ea3850b9ce005e70f502b308edb2d99ca074ed3 git
  • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before e5a3e3cdd9b3015ae79456c81beebfdbb5246c0f git
  • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before b854e1c4eff3473b6d3a9ae74129ac5c48bc0b61 git
Other versions: unaffected
Linux Linux
  • affected 2.6.12
  • unaffected before 2.6.12 semver
  • unaffected 6.12.114 to 6.12.*, inclusive semver
  • unaffected 6.18.58 to 6.18.*, inclusive semver
  • unaffected 6.19.12 to 6.19.*, inclusive semver
  • unaffected 7.0 to *, inclusive original_commit_for_fix
Other versions: affected
Identifiers
CVE-2026-43053
CNA
Linux
Published
1 May 2026
Updated
6 Nov 2026

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.0012, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 1 May 2026, 14:15 UTC Confirmed by the CVE List
  2. 1 May 2026, 15:16 UTC Confirmed by NVD

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.