CVE-2026-31598

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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 possible deadlock between unlink and dio_end_io_write

ocfs2_unlink takes orphan dir inode_lock first and then ip_alloc_sem, while in ocfs2_dio_end_io_write, it acquires these locks in reverse order. This creates an ABBA lock ordering violation on lock classes ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE] and ocfs2_file_ip_alloc_sem_key.

Lock Chain #0 (orphan dir inode_lock -> ip_alloc_sem): ocfs2_unlink ocfs2_prepare_orphan_dir ocfs2_lookup_lock_orphan_dir inode_lock(orphan_dir_inode) <- lock A __ocfs2_prepare_orphan_dir ocfs2_prepare_dir_for_insert ocfs2_extend_dir ocfs2_expand_inline_dir down_write(&oi->ip_alloc_sem) <- Lock B

Lock Chain #1 (ip_alloc_sem -> orphan dir inode_lock): ocfs2_dio_end_io_write down_write(&oi->ip_alloc_sem) <- Lock B ocfs2_del_inode_from_orphan() inode_lock(orphan_dir_inode) <- Lock A

Deadlock Scenario: CPU0 (unlink) CPU1 (dio_end_io_write) ------ ------ inode_lock(orphan_dir_inode) down_write(ip_alloc_sem) down_write(ip_alloc_sem) inode_lock(orphan_dir_inode)

Since ip_alloc_sem is to protect allocation changes, which is unrelated with operations in ocfs2_del_inode_from_orphan. So move ocfs2_del_inode_from_orphan out of ip_alloc_sem to fix the deadlock.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
35.6%
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 possible deadlock between unlink and dio_end_io_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: fix possible deadlock between unlink and dio_end_io_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: fix possible deadlock between unlink and dio_end_io_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: fix possible deadlock between unlink and dio_end_io_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: fix possible deadlock between unlink and dio_end_io_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: fix possible deadlock between unlink and dio_end_io_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b884d52273c60c298bd570163e8053657bbaff6

Vendor Advisories for CVE-2026-31598(2)

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.258—osv

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 47× 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 166 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31598?
CVE-2026-31598 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible deadlock between unlink and dioendio_write ocfs2unlink takes orphan dir inodelock first and then ipallocsem, while in ocfs2dioendiowrite, it acquires these locks in reverse order. This creates an ABBA lock…
When was CVE-2026-31598 disclosed?
CVE-2026-31598 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-31598 actively exploited?
CVE-2026-31598 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31598?
CVE-2026-31598 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31598?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31598, 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-31598

Explore →

Is Your Infrastructure Affected by CVE-2026-31598?

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

Start Free Scan →Browse All CVEs