# CVE-2026-31455: xfs: stop reclaim before pushing AIL during unmount

Status: published. Published: 2026-04-22. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- 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). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.13% as of 2026-11-05; percentile 2.27%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

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

## References

- https://git.kernel.org/stable/c/e6cc490048f78b009259a5f032acead9f789c34c (CNA: Linux)

- https://git.kernel.org/stable/c/239d734c00644072862fa833805c4471573b1445 (CNA: Linux)

- https://git.kernel.org/stable/c/bda27fc0b4eb3a425d9a18475c4cb94fbe862c60 (CNA: Linux)

- https://git.kernel.org/stable/c/d38135af04a3ad8a585c899d176efc8e97853115 (CNA: Linux)

- https://git.kernel.org/stable/c/a89434a6188d8430ea31120da96e3e4cefb58686 (CNA: Linux)

- https://git.kernel.org/stable/c/8147e304d7d32fd5c3e943babc296ce2873dc279 (CNA: Linux)

- https://git.kernel.org/stable/c/558e3275d8a3b101be18a7fe7d1634053e9d9b07 (CNA: Linux)

- https://git.kernel.org/stable/c/4f24a767e3d64a5f58c595b5c29b6063a201f1e3 (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-31455; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-31455; retrieved 2026-11-05; source updated Not reported

Revision: 34fb0001e7575995988778601967da9ec30f3329466a22786462bb0d308838eb

Canonical: https://y2.dev/cve/CVE-2026-31455

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.