CVE-2026-90205

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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

In the Linux kernel, the following vulnerability has been resolved:

ocfs2: validate orphan slot during inode read

Patch series "ocfs2: validate active orphan slots during inode read".

OCFS2 trusts active ordinary and append-DIO orphan slots read from dinodes. A corrupted slot can therefore index osb_orphan_wipes or the slot-local system-inode cache outside their allocations before the corruption is reported.

Patch 1 validates the ordinary orphan slot used by inode wipe processing. Patch 2 validates the append-DIO orphan slot used by DIO completion and orphan recovery. Both checks reject corrupt metadata at the existing inode validation boundary.

This patch (of 2):

[BUG] A corrupted dinode with OCFS2_ORPHANED_FL can carry an i_orphaned_slot outside the mounted filesystem slot range. ocfs2_wipe_inode() uses it to index osb_orphan_wipes before looking up the orphan directory, causing an out-of-bounds memory access.

BUG: KASAN: slab-use-after-free in ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 Read of size 8 at addr ffff88800b767c00 by task kworker/u8:3/85 Call Trace: ... ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 ocfs2_wipe_inode+0x292/0xf70 fs/ocfs2/inode.c:840 ocfs2_delete_inode fs/ocfs2/inode.c:1155 [inline] ocfs2_evict_inode+0x6c9/0x1170 fs/ocfs2/inode.c:1295 evict+0x38e/0x8f0 fs/inode.c:810 iput_final fs/inode.c:1914 [inline] iput fs/inode.c:1966 [inline] iput+0x55b/0x8b0 fs/inode.c:1926 ocfs2_recover_orphans+0x610/0xe40 fs/ocfs2/journal.c:2374 ocfs2_complete_recovery+0x5af/0xd00 fs/ocfs2/journal.c:1373 ...

[CAUSE] ocfs2_validate_inode_block() validates i_suballoc_slot but leaves the active ordinary orphan slot unchecked. Downstream consumers assume that the value is smaller than osb->max_slots.

[FIX] Reject an active i_orphaned_slot outside the slot range during dinode validation, before the inode reaches orphan wipe processing.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

ocfs2: validate orphan slot during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: validate orphan slot during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: validate orphan slot during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d7c4b7ce7b4baedfd8699fa692cd95f77d332de

Vendor Advisories for CVE-2026-90205(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 38× in last 7d / 98× 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.

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

Frequently asked(5)

What is CVE-2026-90205?
CVE-2026-90205 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate orphan slot during inode read Patch series "ocfs2: validate active orphan slots during inode read". OCFS2 trusts active ordinary and append-DIO orphan slots read from dinodes. A corrupted slot can therefore index…
When was CVE-2026-90205 disclosed?
CVE-2026-90205 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90205 actively exploited?
CVE-2026-90205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90205?
CVE-2026-90205 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90205?
No fix for CVE-2026-90205 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90205 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-90205?

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

Book a Demo →Browse All CVEs