CVE-2026-89648

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ceph: cap delegated inode count in ceph_parse_deleg_inos()

ceph_parse_deleg_inos() decodes interval sets of delegated inode numbers from an MDS create-with-delegation reply. For each set it reads a 64-bit start and a 64-bit len with ceph_decode_64_safe(), which only validates that the eight bytes are present in the message, not the value, and then loops over len while inserting entries into s_delegated_inos.

len is fully attacker controlled. A malicious or compromised MDS can send one huge interval, many intervals in one reply, duplicate intervals, or repeated replies that accumulate delegated inodes on the same session. The original code bounded none of these and could spin the insert loop or grow the xarray without limit.

Bound both dimensions with a single enforcement point. Track the number of delegated inodes held by each MDS session in an atomic counter and grow it only in ceph_insert_deleg_ino(), which uses atomic_add_unless() to refuse to push the count past CEPH_MAX_DELEG_INOS. Because that helper is the only place the counter grows, the per-session population can never exceed the cap, so no separate per-session pre-check is needed. The counter is decremented when async create consumes a delegated inode or when an insert fails, incremented when a delegated inode is restored, initialized with the session xarray, and reset when reconnect destroys the xarray.

A per-session cap alone still lets one reply spin the insert loop on duplicate ranges without growing the counter, so also cap the aggregate interval length accepted from a single reply. Together these bound both the loop trip count per reply and the xarray population across replies.

The cap is a fixed, client-chosen constant rather than a value derived from the MDS. mds_client_prealloc_inos is a userspace MDS configuration option; it is never sent to the kernel client on the wire, and a server-supplied bound could not be trusted for a defensive limit in any case. The constant is set well above that option's documented default of 1000 (a generous multiple), so legitimate refill behavior is unaffected while the CPU and xarray memory a malformed delegation stream can consume stays bounded.

Impact: a malicious or compromised Ceph MDS can no longer make a client spin through an unbounded delegated-inode interval or grow one session's delegated-inode xarray without limit.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 13, 2026

Advisory Details (3)

Auto-updated Sep 13, 2026
Patch available.
Web page

ceph: cap delegated inode count in ceph_parse_deleg_inos() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f341270ac5f5077804d7837ce77b0f0df1cea29d
Web page

ceph: cap delegated inode count in ceph_parse_deleg_inos() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c040e139f1a629b767f900bbbc3f9892c290ed85
Web page

ceph: cap delegated inode count in ceph_parse_deleg_inos() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-89648(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 33× in last 7d / 168× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 181 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 82 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-89648?
CVE-2026-89648 is a high-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: ceph: cap delegated inode count in cephparsedeleg_inos() cephparsedeleg_inos() decodes interval sets of delegated inode numbers from an MDS create-with-delegation reply. For each set it reads a 64-bit start and a 64-bit len with…
When was the CVE record for CVE-2026-89648 published?
The CVE record for CVE-2026-89648 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 13, 2026; the record at its source may have been updated since.
Is CVE-2026-89648 actively exploited?
CVE-2026-89648 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89648?
CVE-2026-89648 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89648?
A fix for CVE-2026-89648 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89648 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-89648

Explore →

Is Your Infrastructure Affected by CVE-2026-89648?

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