diff options
author | Jeff Layton <jlayton@kernel.org> | 2025-06-19 06:01:55 -0400 |
---|---|---|
committer | Chuck Lever <chuck.lever@oracle.com> | 2025-06-19 09:35:45 -0400 |
commit | 94d10a4dba0bc482f2b01e39f06d5513d0f75742 (patch) | |
tree | a1a350ca5c17462bfb122ae8743f5a6b282e1aa3 /fs/bcachefs/sb-errors.c | |
parent | 8ea688a3372e8369dc04395b39b4e71a6d91d4d5 (diff) |
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.
Cc: stable@kernel.org
Fixes: 29cd2927fb91 ("SUNRPC: Fix encoding of accepted but unsuccessful RPC replies")
Reported-by: tianshuo han <hantianshuo233@gmail.com>
Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'fs/bcachefs/sb-errors.c')
0 files changed, 0 insertions, 0 deletions