### [CVE-2025-38089](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-38089)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=29cd2927fb914cc53b5ba4f67d2b74695c994ba4%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=6.4%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=9b59f5c4911e87264507e0934cd2bb277390c560%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)

### Description

In the Linux kernel, the following vulnerability has been resolved:sunrpc: handle SVC_GARBAGE during svc auth processing as auth errortianshuo han reported a remotely-triggerable crash if the client sends akernel RPC server a specially crafted packet. If decoding the RPC replyfails in such a way that SVC_GARBAGE is returned without setting therq_accept_statp pointer, then that pointer can be dereferenced and avalue stored there.If it's the first time the thread has processed an RPC, then thatpointer 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_authenticateor pg_authenticate as if it should send a GARBAGE_ARGS reply. RFC 5531says that if authentication fails that the RPC should be rejectedinstead with a status of AUTH_ERR.Handle a SVC_GARBAGE return as an AUTH_ERROR, with a reason ofAUTH_BADCRED instead of returning GARBAGE_ARGS in that case. Thissidesteps the whole problem of touching the rpc_accept_statp pointer inthis situation and avoids the crash.

### POC

#### Reference
- https://github.com/keymaker-arch/NFSundown
- https://www.openwall.com/lists/oss-security/2025/07/02/2

#### Github
- https://github.com/PuddinCat/GithubRepoSpider
- https://github.com/keymaker-arch/NFSundown
- https://github.com/nomi-sec/PoC-in-GitHub