CVE-2026-31589

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-24. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 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:

mm: call ->free_folio() directly in folio_unmap_invalidate()

We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we've already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping->a_ops.

Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
35.9%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (4)

Auto-updated Jun 20, 2026
No patch confirmed yet.
generic

mm: call ->free_folio() directly in folio_unmap_invalidate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/615d9bb2ccad42f9e21d837431e401db2e471195
generic

mm: call ->free_folio() directly in folio_unmap_invalidate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm: call ->free_folio() directly in folio_unmap_invalidate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm: call ->free_folio() directly in folio_unmap_invalidate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/efc52947247a21bbf79059539bbbd40f4ea76f00

Vendor Advisories for CVE-2026-31589(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 295 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31589?
CVE-2026-31589 is a critical vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: mm: call ->freefolio() directly in foliounmap_invalidate() We can only call filemapfreefolio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we've already removed the folio from the mapping so it no longer…
When was CVE-2026-31589 disclosed?
CVE-2026-31589 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31589 actively exploited?
CVE-2026-31589 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31589?
CVE-2026-31589 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31589?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31589, 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

Explore the affected products and dependency analysis for CVE-2026-31589

Explore →

Is Your Infrastructure Affected by CVE-2026-31589?

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

Start Free Scan →Browse All CVEs