CVE-2025-38089: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: handle SVCGARBAGE 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 SVCGARBAGE is returned without setting the rqacceptstatp 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 SVCGARBAGE return from svcauthenticate or pgauthenticate as if it should send a GARBAGEARGS reply. RFC 5531 says that if authentication fails that the RPC should be rejected instead with a status of AUTHERR.
Handle a SVCGARBAGE return as an AUTHERROR, with a reason of AUTHBADCRED instead of returning GARBAGEARGS in that case. This sidesteps the whole problem of touching the rpcacceptstatp pointer in this situation and avoids the crash.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38089?
CVE-2025-38089 has been rated as a critical severity vulnerability due to its potential for remote exploitation leading to a crash of the kernel RPC server.
How do I fix CVE-2025-38089?
To mitigate CVE-2025-38089, users should update their Linux kernel to a version where the vulnerability has been patched.
Who reported CVE-2025-38089?
CVE-2025-38089 was reported by Tianshuo Han, highlighting a remotely-triggerable crash risk.
What types of systems are affected by CVE-2025-38089?
CVE-2025-38089 affects systems running the Linux kernel that utilize the kernel RPC server functionality.
What is the impact of exploiting CVE-2025-38089?
Exploitation of CVE-2025-38089 can lead to a denial of service due to a crash of the kernel RPC server upon receiving a specially crafted packet.