Answer in brief
CVE-2026-45870 records a Medium severity (CVSS 5.5) vulnerability in SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths. 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.
Answer in brief
CVE-2026-45870 records a Medium severity (CVSS 5.5) vulnerability in SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths. 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.
CVSS is 5.5. 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 <c81431b1b9fbd21e9a5a9211b5517b7295d18e6a || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <caf7eff432e91a9eba1c79fa545c2f54be15d62b || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <64303b92d94c0c7845a273acd8d84b796d6f1db7 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <df10f23defff22c8d55fe6db74f6e4ce927145bf || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <b4af3806846778799cd4ab0766dc18341e777264 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <d79b9097a6a2b91471b40755f1225364be5d85ff || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <3b56eb90feb8a3709417f5624f3871847d42bcb1 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <3e6397b056335cc56ef0e9da36c95946a19f5118 | c81431b1b9fbd21e9a5a9211b5517b7295d18e6a, caf7eff432e91a9eba1c79fa545c2f54be15d62b, 64303b92d94c0c7845a273acd8d84b796d6f1db7, df10f23defff22c8d55fe6db74f6e4ce927145bf, b4af3806846778799cd4ab0766dc18341e777264, d79b9097a6a2b91471b40755f1225364be5d85ff, 3b56eb90feb8a3709417f5624f3871847d42bcb1, 3e6397b056335cc56ef0e9da36c95946a19f5118 |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 5.5. 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 <c81431b1b9fbd21e9a5a9211b5517b7295d18e6a || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <caf7eff432e91a9eba1c79fa545c2f54be15d62b || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <64303b92d94c0c7845a273acd8d84b796d6f1db7 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <df10f23defff22c8d55fe6db74f6e4ce927145bf || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <b4af3806846778799cd4ab0766dc18341e777264 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <d79b9097a6a2b91471b40755f1225364be5d85ff || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <3b56eb90feb8a3709417f5624f3871847d42bcb1 || >=1d658336b05f8697d6445834f8867f8ad5e4f735 <3e6397b056335cc56ef0e9da36c95946a19f5118 | c81431b1b9fbd21e9a5a9211b5517b7295d18e6a, caf7eff432e91a9eba1c79fa545c2f54be15d62b, 64303b92d94c0c7845a273acd8d84b796d6f1db7, df10f23defff22c8d55fe6db74f6e4ce927145bf, b4af3806846778799cd4ab0766dc18341e777264, d79b9097a6a2b91471b40755f1225364be5d85ff, 3b56eb90feb8a3709417f5624f3871847d42bcb1, 3e6397b056335cc56ef0e9da36c95946a19f5118 |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.