CVE-2026-3497: Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions.
Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself. The usage of sshpkt_disconnect() on an error, which does not terminate the process, allows an attacker to send an unexpected GSSAPI message type during the GSSAPI key exchange to the server, which will call the underlying function and continue the execution of the program without setting the related connection variables. As the variables are not initialized to NULL the code later accesses those uninitialized variables, accessing random memory, which could lead to undefined behavior. The recommended workaround is to use ssh_packet_disconnect() instead, which does terminate the process. The impact of the vulnerability depends heavily on the compiler flag hardening configuration.
Security readout for executives and security teams
Plain-English summary
A flaw in distribution-added OpenSSH GSSAPI code can let an unauthenticated remote attacker crash an affected SSH server and potentially expose limited memory. Upstream OpenSSH is not affected. Actual impact varies with compiler hardening, so organizations must assess distribution packages rather than relying only on the upstream OpenSSH version.
Executive priority
Treat this as a high-priority patching issue for exposed Linux SSH servers, especially where GSSAPI is available. It is not evidence of an upstream OpenSSH-wide emergency or confirmed active exploitation. Request rapid inventory and vendor-update deployment, with operational monitoring until coverage is verified.
Technical view
During GSSAPI key exchange, an unexpected message invokes sshpkt_disconnect(), which does not terminate processing. Execution continues without initializing connection variables, leading to access of indeterminate memory and undefined behavior. The CVSS 3.1 score is 8.2, reflecting network access, low complexity, no privileges or interaction, limited confidentiality impact, and high availability impact.
Likely exposure
Exposure is concentrated in Linux distributions carrying the affected GSSAPI patch, including identified Ubuntu OpenSSH package versions and products covered by Debian and Red Hat advisories. Internet-reachable SSH services using the affected package and GSSAPI path deserve priority. Upstream-only OpenSSH builds are outside the described scope.
Exploitation context
The vulnerable path is reachable remotely before authentication during GSSAPI key exchange. The supplied record is not in KEV and provides no evidence of active exploitation. Undefined behavior may cause denial of service or limited memory disclosure; practical results depend heavily on build-time compiler hardening.
Researcher notes
Assessment should distinguish downstream GSSAPI deltas from upstream OpenSSH. Review the unexpected-message error path, variable initialization, process termination semantics, and compiler hardening. The supplied evidence supports undefined memory access, availability loss, and limited confidentiality impact, but does not establish reliable code execution or exploitation in the wild.
Mitigation direction
Apply the applicable Linux distributor's security update or erratum after normal compatibility testing.
Prioritize affected SSH servers that are internet-reachable or permit GSSAPI authentication.
Downstream maintainers should replace sshpkt_disconnect() with the terminating ssh_packet_disconnect(), following vendor guidance.
Consult the exact distributor advisory when no confirmed fixed package is available.
Validation and detection
Inventory OpenSSH packages by distribution, release, architecture, and installed package version.
Compare installed packages with Ubuntu, Debian, or Red Hat advisory status and fixed builds.
Identify whether GSSAPI authentication is enabled and reachable on each affected SSH service.
After updating, confirm package provenance, restart requirements, and successful SSH authentication.
Monitor SSH service crashes and abnormal GSSAPI negotiation failures while remediation proceeds.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-824: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-824 · source CWE mapping
Access of Uninitialized Pointer
Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.