CVE-2026-31455

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 22, 2026

Last Modified

June 5, 2026

Advisory Details (8)

Auto-updated May 5, 2026
No patch confirmed yet.
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e6cc490048f78b009259a5f032acead9f789c34c
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d38135af04a3ad8a585c899d176efc8e97853115
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bda27fc0b4eb3a425d9a18475c4cb94fbe862c60
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a89434a6188d8430ea31120da96e3e4cefb58686
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8147e304d7d32fd5c3e943babc296ce2873dc279
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/558e3275d8a3b101be18a7fe7d1634053e9d9b07
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f24a767e3d64a5f58c595b5c29b6063a201f1e3
generic

xfs: stop reclaim before pushing AIL during unmount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/239d734c00644072862fa833805c4471573b1445

Vendor Advisories for CVE-2026-31455(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(23)

Data Freshness Timeline

(refreshed 5× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 249 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-02 03:04 UTCOSV refresh
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 14:17 UTCEPSS rescore
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 06:01 UTCEG score recompute
  4. 2026-08-16 06:01 UTCVendor advisory
  5. 2026-08-16 06:01 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 16:08 UTCVendor advisory
  9. 2026-08-14 16:08 UTCGHSA enrichment
  10. 2026-08-14 04:20 UTCEG score recompute
  11. 2026-08-14 04:20 UTCVendor advisory
  12. 2026-08-14 04:20 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 08:40 UTCVendor advisory
  15. 2026-08-13 08:39 UTCGHSA enrichment
  16. 2026-08-12 18:32 UTCEG score recompute
  17. 2026-08-12 18:32 UTCVendor advisory
  18. 2026-08-12 18:32 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 16:47 UTCEG score recompute
  21. 2026-08-11 16:47 UTCVendor advisory
  22. 2026-08-11 16:47 UTCGHSA enrichment
  23. 2026-08-11 02:22 UTCEG score recompute
  24. 2026-08-11 02:22 UTCVendor advisory
  25. 2026-08-11 02:22 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 03:10 UTCVendor advisory
  28. 2026-08-10 03:10 UTCGHSA enrichment
  29. 2026-08-09 15:21 UTCEG score recompute
  30. 2026-08-09 15:21 UTCVendor advisory
  31. 2026-08-09 15:21 UTCGHSA enrichment
  32. 2026-08-09 13:46 UTCEPSS rescore
  33. 2026-08-09 03:33 UTCEG score recompute
  34. 2026-08-09 03:33 UTCVendor advisory
  35. 2026-08-09 03:33 UTCGHSA enrichment
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-08 12:29 UTCVendor advisory
  38. 2026-08-08 12:29 UTCGHSA enrichment
  39. 2026-08-08 00:38 UTCEG score recompute
  40. 2026-08-08 00:38 UTCVendor advisory
  41. 2026-08-08 00:38 UTCGHSA enrichment
  42. 2026-08-07 12:50 UTCEG score recompute
  43. 2026-08-07 12:50 UTCVendor advisory
  44. 2026-08-07 12:50 UTCGHSA enrichment
  45. 2026-08-06 13:46 UTCEPSS rescore
  46. 2026-08-06 11:29 UTCVendor advisory
  47. 2026-08-06 11:29 UTCGHSA enrichment
  48. 2026-08-05 23:05 UTCEG score recompute
  49. 2026-08-05 23:05 UTCVendor advisory
  50. 2026-08-05 23:05 UTCGHSA enrichment
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:38 UTCEPSS rescore
  54. 2026-08-03 21:15 UTCEG score recompute
  55. 2026-08-03 21:15 UTCVendor advisory
  56. 2026-08-03 21:15 UTCGHSA enrichment
  57. 2026-08-03 10:36 UTCEPSS rescore
  58. 2026-08-03 00:42 UTCVendor advisory
  59. 2026-08-03 00:42 UTCGHSA enrichment
  60. 2026-08-02 12:31 UTCEG score recompute
  61. 2026-08-02 12:31 UTCVendor advisory
  62. 2026-08-02 12:31 UTCGHSA enrichment
  63. 2026-08-02 02:27 UTCEPSS rescore
  64. 2026-07-30 16:27 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-23 14:18 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 03:08 UTCEG score recompute
  73. 2026-07-22 14:08 UTCEPSS rescore
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:24 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31455?
CVE-2026-31455 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: xfs: stop reclaim before pushing AIL during unmount The unmount sequence in xfsunmountflush_inodes() pushed the AIL while background reclaim and inodegc are still running. This is broken independently of any use-after-free issues -…
When was CVE-2026-31455 disclosed?
CVE-2026-31455 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on June 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31455 actively exploited?
CVE-2026-31455 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-31455?
CVE-2026-31455 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31455?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31455, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31455

Explore →

Is Your Infrastructure Affected by CVE-2026-31455?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.