Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2026-89538

In the Linux kernel's SUNRPC implementation, the gss_krb5_unwrap_v2 function incorrectly handles Kerberos v2 wrap tokens that have an oversized 'extra count' (ec) field. Although the field is authenticated, a peer with a valid GSS context can encrypt a token where ec exceeds the plaintext length, leaving the internal buffer in an inconsistent state after processing. This flaw can be exploited to cause a denial‑of‑service or other impacts and is rated critical with a CVSS base score of 9.8.

publishedSep 11, 2026
last modifiedSep 13, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
10th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Oct 13, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel (specific versions not listed in the provided data).

02

Real-world impact

An attacker with a valid GSS context could send a malformed Kerberos v2 token that triggers inconsistent buffer state, potentially leading to service disruption or other adverse effects.

03

Why this severity

CVSS 3.1 score: 9.8 (Critical) – Attack Vector: Network, Attack Complexity: Low, Privileges Required: None, User Interaction: None, Scope: Unchanged, Confidentiality: High, Integrity: High, Availability: High.

04

What to do about it

official fix available
recommended steps
  1. 01Update the Linux kernel to a version that includes the patch for CVE-2026-89538 (the vulnerability has been marked as resolved in the kernel).
  2. 02Reboot the system or restart affected services after applying the kernel update.

NVD description states the vulnerability has been resolved in the Linux kernel.

05

Timeline

  1. Sep 11, 2026 · 2d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Sep 13, 2026 · 5h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →