Answer in brief
CVE-2026-89539 records a Unknown severity vulnerability in SUNRPC: reject duplicate CREDS_VALUE options. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1d658336b05f8697d6445834f8867f8ad5e4f735 <f615b884310bf82d0014e3b5a92eb9aa88146685 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <7a1d0501cbb962beba23377035d667bf3c1726ee || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <9d94f046b23de0f77849ea69133063c949297e30 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <2e4ce62385c1b8a887c5370af058ac7b52a8eaf9 | f615b884310bf82d0014e3b5a92eb9aa88146685, 7a1d0501cbb962beba23377035d667bf3c1726ee, 9d94f046b23de0f77849ea69133063c949297e30, 2e4ce62385c1b8a887c5370af058ac7b52a8eaf9 |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.