Public vulnerability disclosure

CVE-2026-31455

xfs: stop reclaim before pushing AIL during unmount

published

In the Linux kernel, the following vulnerability has been resolved: xfs: stop reclaim before pushing AIL during unmount The unmount sequence in xfs_unmount_flush_inodes() pushed the AIL while background reclaim and inodegc are still running. This is broken independently of any use-after-free issues - background reclaim and inodegc should not be running while the AIL is being pushed during unmount, as inodegc can dirty and insert inodes into the AIL during the flush, and background reclaim can race to abort and free dirty inodes. Reorder xfs_unmount_flush_inodes() to stop inodegc and cancel background reclaim before pushing the AIL. Stop inodegc before cancelling m_reclaim_work because the inodegc worker can re-queue m_reclaim_work via xfs_inodegc_set_reclaimable.

Technical severityUnscoredNo score in collected sources
Published2026-04-22Source updated 2026-11-05
Collected2026-11-052 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < e6cc490048f78b009259a5f032acead9f789c34c (affected, git)
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < 239d734c00644072862fa833805c4471573b1445 (affected, git)
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < bda27fc0b4eb3a425d9a18475c4cb94fbe862c60 (affected, git)
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < d38135af04a3ad8a585c899d176efc8e97853115 (affected, git)
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < a89434a6188d8430ea31120da96e3e4cefb58686 (affected, git)
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < 8147e304d7d32fd5c3e943babc296ce2873dc279 (affected, git)
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < 558e3275d8a3b101be18a7fe7d1634053e9d9b07 (affected, git)
≥ 90c60e16401248a4900f3f9387f563d0178dcf34; < 4f24a767e3d64a5f58c595b5c29b6063a201f1e3 (affected, git)
Other versions: unaffected
CNA: Linux
Linux
Linux
5.9 (affected)
≥ 0; < 5.9 (unaffected, semver)
≥ 5.10.253; ≤ 5.10.* (unaffected, semver)
≥ 5.15.203; ≤ 5.15.* (unaffected, semver)
≥ 6.1.168; ≤ 6.1.* (unaffected, semver)
≥ 6.6.131; ≤ 6.6.* (unaffected, semver)
≥ 6.12.80; ≤ 6.12.* (unaffected, semver)
≥ 6.18.21; ≤ 6.18.* (unaffected, semver)
≥ 6.19.11; ≤ 6.19.* (unaffected, semver)
≥ 7.0; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide