Answer in brief
CVE-2025-38089 records a Unknown severity vulnerability in sunrpc: handle SVC_GARBAGE during svc auth processing as auth error. 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 | >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <599c489eea793821232a2f69a00fa57d82b0ac98 || >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <353e75b55e583635bf71cde6abcec274dba05edd || >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <c90459cd58bb421d275337093d8e901e0ba748dd || >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <94d10a4dba0bc482f2b01e39f06d5513d0f75742 || 9b59f5c4911e87264507e0934cd2bb277390c560 || >=6.3.4 <6.4 | 599c489eea793821232a2f69a00fa57d82b0ac98, 353e75b55e583635bf71cde6abcec274dba05edd, c90459cd58bb421d275337093d8e901e0ba748dd, 94d10a4dba0bc482f2b01e39f06d5513d0f75742, 6.4 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Jun 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error tianshuo han reported a remotely-triggerable crash if the client sends a kernel RPC server a specially crafted packet. If decoding the RPC reply fails in such a way that SVC_GARBAGE is returned without setting the rq_accept_statp pointer, then that pointer can be dereferenced and a value stored there. If it's the first time the thread has processed an RPC, then that pointer will be set to NULL and the kernel will crash. In other cases, it could create a memory scribble. The server sunrpc code treats a SVC_GARBAGE return from svc_authenticate or pg_authenticate as if it should send a GARBAGE_ARGS reply. RFC 5531 says that if authentication fails that the RPC should be rejected instead with a status of AUTH_ERR. Handle a SVC_GARBAGE return as an AUTH_ERROR, with a reason of AUTH_BADCRED instead of returning GARBAGE_ARGS in that case. This sidesteps the whole problem of touching the rpc_accept_statp pointer in this situation and avoids the crash.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38089 records a Unknown severity vulnerability in sunrpc: handle SVC_GARBAGE during svc auth processing as auth error. 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 | >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <599c489eea793821232a2f69a00fa57d82b0ac98 || >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <353e75b55e583635bf71cde6abcec274dba05edd || >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <c90459cd58bb421d275337093d8e901e0ba748dd || >=29cd2927fb914cc53b5ba4f67d2b74695c994ba4 <94d10a4dba0bc482f2b01e39f06d5513d0f75742 || 9b59f5c4911e87264507e0934cd2bb277390c560 || >=6.3.4 <6.4 | 599c489eea793821232a2f69a00fa57d82b0ac98, 353e75b55e583635bf71cde6abcec274dba05edd, c90459cd58bb421d275337093d8e901e0ba748dd, 94d10a4dba0bc482f2b01e39f06d5513d0f75742, 6.4 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Jun 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error tianshuo han reported a remotely-triggerable crash if the client sends a kernel RPC server a specially crafted packet. If decoding the RPC reply fails in such a way that SVC_GARBAGE is returned without setting the rq_accept_statp pointer, then that pointer can be dereferenced and a value stored there. If it's the first time the thread has processed an RPC, then that pointer will be set to NULL and the kernel will crash. In other cases, it could create a memory scribble. The server sunrpc code treats a SVC_GARBAGE return from svc_authenticate or pg_authenticate as if it should send a GARBAGE_ARGS reply. RFC 5531 says that if authentication fails that the RPC should be rejected instead with a status of AUTH_ERR. Handle a SVC_GARBAGE return as an AUTH_ERROR, with a reason of AUTH_BADCRED instead of returning GARBAGE_ARGS in that case. This sidesteps the whole problem of touching the rpc_accept_statp pointer in this situation and avoids the crash.
Quoted source text, attributed separately from HOL analysis.