CVE-2026-89539

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

SUNRPC: reject duplicate CREDS_VALUE options

gssx_dec_option_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssx_dec_linux_creds() on the same struct svc_cred. That helper unconditionally installs a fresh groups_alloc() result into creds->cr_group_info without releasing whatever pointer was already there:

for (i = 0; i < count; i++) { ... decode name ... if (length == sizeof(CREDS_VALUE) && memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) { err = gssx_dec_linux_creds(xdr, creds); ... } }

A reply that carries two CREDS_VALUE entries therefore overwrites cr_group_info on the second iteration and orphans the group_info allocated by the first call. The earlier free_creds path only releases the last cr_group_info via free_svc_cred(), so the first allocation's refcount stays at one and its kvmalloc-backed storage is leaked. No in-tree caller of gssp_accept_sec_context_upcall() expects more than one CREDS_VALUE per reply.

Fix by tracking whether a CREDS_VALUE option has already been decoded and returning -EINVAL on any subsequent match, so the free_creds path releases the single group_info that was installed.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

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 11, 2026

Vendor Advisories for CVE-2026-89539(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-12 14:48 UTCEG score recompute
  4. 2026-10-11 19:15 UTCEG score recompute
  5. 2026-10-11 16:32 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-11 13:47 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-09 19:16 UTCVendor advisory
  11. 2026-10-09 19:16 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-06 14:14 UTCVendor advisory
  16. 2026-10-06 14:14 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  17. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-03 12:06 UTCVendor advisory
  20. 2026-10-03 12:06 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  21. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-30 09:35 UTCEG score recompute
  24. 2026-09-30 09:35 UTCVendor advisory
  25. 2026-09-30 09:35 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
Show 28 more
  1. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-09-27 07:17 UTCVendor advisory
  4. 2026-09-27 07:17 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-09-24 05:09 UTCVendor advisory
  8. 2026-09-24 05:09 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-09-21 03:00 UTCVendor advisory
  13. 2026-09-21 03:00 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-09-18 00:52 UTCVendor advisory
  17. 2026-09-18 00:52 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  18. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-14 22:44 UTCEG score recompute
  23. 2026-09-14 22:44 UTCGHSA enrichmentGHSA-j7j8-rmpg-46w5
  24. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-11 20:36 UTCNVD update
  27. 2026-09-11 19:50 UTCEG score recompute
  28. 2026-09-11 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89539?
CVE-2026-89539 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: SUNRPC: reject duplicate CREDS_VALUE options gssxdecoption_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssxdeclinuxcreds() on the same struct svccred. That helper…
When was the CVE record for CVE-2026-89539 published?
The CVE record for CVE-2026-89539 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 11, 2026; the record at its source may have been updated since.
Is CVE-2026-89539 actively exploited?
CVE-2026-89539 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89539?
A fix for CVE-2026-89539 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89539 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-89539

Explore →

Is Your Infrastructure Affected by CVE-2026-89539?

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