CVE-2026-45870
SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths The gssx_dec_ctx(), gssx_dec_status(), and gssx_dec_name() functions allocate memory via gssx_dec_buffer(), which calls kmemdup(). When a subsequent decode operation fails, these functions return immediately without freeing previously allocated buffers, causing memory leaks. The leak in gssx_dec_ctx() is particularly relevant because the caller (gssp_accept_sec_context_upcall) initializes several buffer length fields to non-zero values, resulting in memory allocation: struct gssx_ctx rctxh = { .exported_context_token.len = GSSX_max_output_handle_sz, .mech.len = GSS_OID_MAX_LEN, .src_name.display_name.len = GSSX_max_princ_sz, .targ_name.display_name.len = GSSX_max_princ_sz }; If, for example, gssx_dec_name() succeeds for src_name but fails for targ_name, the memory allocated for exported_context_token, mech, and src_name.display_name remains unreferenced and cannot be reclaimed. Add error handling with goto-based cleanup to free any previously allocated buffers before returning an error.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < c81431b1b9fbd21e9a5a9211b5517b7295d18e6a (affected, git) ≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < caf7eff432e91a9eba1c79fa545c2f54be15d62b (affected, git) ≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < 64303b92d94c0c7845a273acd8d84b796d6f1db7 (affected, git) ≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < df10f23defff22c8d55fe6db74f6e4ce927145bf (affected, git) ≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < b4af3806846778799cd4ab0766dc18341e777264 (affected, git) ≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < d79b9097a6a2b91471b40755f1225364be5d85ff (affected, git) ≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < 3b56eb90feb8a3709417f5624f3871847d42bcb1 (affected, git) ≥ 1d658336b05f8697d6445834f8867f8ad5e4f735; < 3e6397b056335cc56ef0e9da36c95946a19f5118 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
3.10 (affected) ≥ 0; < 3.10 (unaffected, semver) ≥ 5.10.252; ≤ 5.10.* (unaffected, semver) ≥ 5.15.202; ≤ 5.15.* (unaffected, semver) ≥ 6.1.165; ≤ 6.1.* (unaffected, semver) ≥ 6.6.128; ≤ 6.6.* (unaffected, semver) ≥ 6.12.75; ≤ 6.12.* (unaffected, semver) ≥ 6.18.14; ≤ 6.18.* (unaffected, semver) ≥ 6.19.4; ≤ 6.19.* (unaffected, semver) ≥ 7.0; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/c81431b1b9fbd21e9a5a9211b5517b7295d18e6aCNA: Linux
- https://git.kernel.org/stable/c/caf7eff432e91a9eba1c79fa545c2f54be15d62bCNA: Linux
- https://git.kernel.org/stable/c/64303b92d94c0c7845a273acd8d84b796d6f1db7CNA: Linux
- https://git.kernel.org/stable/c/df10f23defff22c8d55fe6db74f6e4ce927145bfCNA: Linux
- https://git.kernel.org/stable/c/b4af3806846778799cd4ab0766dc18341e777264CNA: Linux
- https://git.kernel.org/stable/c/d79b9097a6a2b91471b40755f1225364be5d85ffCNA: Linux
- https://git.kernel.org/stable/c/3b56eb90feb8a3709417f5624f3871847d42bcb1CNA: Linux
- https://git.kernel.org/stable/c/3e6397b056335cc56ef0e9da36c95946a19f5118CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.