CVE-2026-31597

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY

filemap_fault() may drop the mmap_lock before returning VM_FAULT_RETRY, as documented in mm/filemap.c:

"If our return value has VM_FAULT_RETRY set, it's because the mmap_lock may be dropped before doing I/O or by lock_folio_maybe_drop_mmap()."

When this happens, a concurrent munmap() can call remove_vma() and free the vm_area_struct via RCU. The saved 'vma' pointer in ocfs2_fault() then becomes a dangling pointer, and the subsequent trace_ocfs2_fault() call dereferences it -- a use-after-free.

Fix this by saving ip_blkno as a plain integer before calling filemap_fault(), and removing vma from the trace event. Since ip_blkno is copied by value before the lock can be dropped, it remains valid regardless of what happens to the vma or inode afterward.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.8%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (6)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/925bf22c1b823e231b1baea761fe8a1512e442f2
generic

ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7de554cabf160e331e4442e2a9ad874ca9875921
generic

ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76a602fdbb78dd05b2da06f74a988cebc97e82d0
generic

ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f072daefcab1d84ce37c073645615f63be91006
generic

ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4cf2768a0291a0cdd0dae801ea0eafa3878a349d

Vendor Advisories for CVE-2026-31597(2)

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 8× in last 7d / 38× 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 164 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31597?
CVE-2026-31597 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix use-after-free in ocfs2fault() when VMFAULT_RETRY filemapfault() may drop the mmaplock before returning VMFAULTRETRY, as documented in mm/filemap.c: "If our return value has VMFAULTRETRY set, it's because the mmap_lock…
When was CVE-2026-31597 disclosed?
CVE-2026-31597 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-31597 actively exploited?
CVE-2026-31597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31597?
CVE-2026-31597 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31597?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31597, 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-31597

Explore →

Is Your Infrastructure Affected by CVE-2026-31597?

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