FlawAtlas
Search the atlas
CVE-2025-38089 Not scored

sunrpc: handle SVC_GARBAGE during svc auth processing as auth error

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.

Exploit probability 0.3%
Published June 30, 2025
Required by Not available
Last source change July 15, 2026

02 / AFFECTED SOFTWARE

Affected packages

Linux Kernel
Unknown Unknown

773 explicit affected versions

03 / CONNECTIONS

Connected vulnerabilities

related ALSA-2025:11411
related ALSA-2025:11428
related OPENSUSE-SU-2025:20081-1
related SUSE-SU-2025:02853-1
related SUSE-SU-2025:02923-1
related SUSE-SU-2025:02969-1
related SUSE-SU-2025:02996-1
related SUSE-SU-2025:02997-1
related SUSE-SU-2025:03011-1
related SUSE-SU-2025:03023-1
related SUSE-SU-2025:03465-1
related SUSE-SU-2025:03468-1
related SUSE-SU-2025:03469-1
related SUSE-SU-2025:03470-1
related SUSE-SU-2025:03472-1
related SUSE-SU-2025:03476-1
related SUSE-SU-2025:03480-1
related SUSE-SU-2025:03494-1
related SUSE-SU-2025:03495-1
related SUSE-SU-2025:03563-1
related SUSE-SU-2025:03566-1
related SUSE-SU-2025:03567-1
related SUSE-SU-2025:03569-1
related SUSE-SU-2025:03571-1
related SUSE-SU-2025:03572-1
related SUSE-SU-2025:03575-1
related SUSE-SU-2025:20577-1
related SUSE-SU-2025:20586-1
related SUSE-SU-2025:20601-1
related SUSE-SU-2025:20602-1
related SUSE-SU-2025:20806-1
related SUSE-SU-2025:20807-1
related SUSE-SU-2025:20808-1
related SUSE-SU-2025:20809-1
related SUSE-SU-2025:20810-1
related SUSE-SU-2025:20811-1
related SUSE-SU-2025:20813-1
related SUSE-SU-2025:20814-1
related SUSE-SU-2025:20815-1
related SUSE-SU-2025:20816-1
related SUSE-SU-2025:20817-1
related SUSE-SU-2025:20818-1
related SUSE-SU-2025:20819-1
related SUSE-SU-2025:20826-1
related SUSE-SU-2025:20827-1
related SUSE-SU-2025:20828-1
related SUSE-SU-2025:20829-1
related SUSE-SU-2025:20830-1
related SUSE-SU-2025:20831-1
related SUSE-SU-2025:20832-1
related SUSE-SU-2025:20833-1
related SUSE-SU-2025:20834-1
related SUSE-SU-2025:20835-1
related SUSE-SU-2025:20836-1
related SUSE-SU-2025:20837-1
related SUSE-SU-2025:20838-1
related SUSE-SU-2025:20840-1
related SUSE-SU-2025:20841-1
related SUSE-SU-2025:21074-1
related SUSE-SU-2025:21139-1
related SUSE-SU-2025:21179-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2025-38089

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.

View original source

05 / REFERENCES

Further evidence