Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31455

xfs: stop reclaim before pushing AIL during unmount

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31455, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < e6cc490048f78b009259a5f032acead9f789c34c
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 239d734c00644072862fa833805c4471573b1445
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < bda27fc0b4eb3a425d9a18475c4cb94fbe862c60
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < d38135af04a3ad8a585c899d176efc8e97853115
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < a89434a6188d8430ea31120da96e3e4cefb58686
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 8147e304d7d32fd5c3e943babc296ce2873dc279
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 558e3275d8a3b101be18a7fe7d1634053e9d9b07
    • affected 90c60e16401248a4900f3f9387f563d0178dcf34 – < 4f24a767e3d64a5f58c595b5c29b6063a201f1e3
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31455 badge
[![CVE-2026-31455](https://cveledger.app/badge/CVE-2026-31455.svg)](https://cveledger.app/cve/CVE-2026-31455)

Record last updated .