[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d0f4a2ab-7010-5b09-f47e-21dc54a759c2@gmail.com>
Date: Thu, 21 Sep 2023 13:30:25 +0100
From: Pavel Begunkov <asml.silence@...il.com>
To: Paolo Abeni <pabeni@...hat.com>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>,
Jordan Rife <jrife@...gle.com>, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, netdev@...r.kernel.org
Cc: dborkman@...nel.org, stable@...r.kernel.org, Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH net v4 2/3] net: prevent rewrite of msg_name in
sock_sendmsg()
On 9/21/23 09:32, Paolo Abeni wrote:
> On Wed, 2023-09-20 at 09:28 -0400, Willem de Bruijn wrote:
>> Jordan Rife wrote:
>>> Callers of sock_sendmsg(), and similarly kernel_sendmsg(), in kernel
>>> space may observe their value of msg_name change in cases where BPF
>>> sendmsg hooks rewrite the send address. This has been confirmed to break
>>> NFS mounts running in UDP mode and has the potential to break other
>>> systems.
>>>
>>> This patch:
>>>
>>> 1) Creates a new function called __sock_sendmsg() with same logic as the
>>> old sock_sendmsg() function.
>>> 2) Replaces calls to sock_sendmsg() made by __sys_sendto() and
>>> __sys_sendmsg() with __sock_sendmsg() to avoid an unnecessary copy,
>>> as these system calls are already protected.
>>> 3) Modifies sock_sendmsg() so that it makes a copy of msg_name if
>>> present before passing it down the stack to insulate callers from
>>> changes to the send address.
>>>
>>> Link: https://lore.kernel.org/netdev/20230912013332.2048422-1-jrife@google.com/
>>> Fixes: 1cedee13d25a ("bpf: Hooks for sys_sendmsg")
>>> Cc: stable@...r.kernel.org
>>> Signed-off-by: Jordan Rife <jrife@...gle.com>
>>
>> Reviewed-by: Willem de Bruijn <willemb@...gle.com>
>
> CC Jens and Pavel, as I guess io_uring likely want to use
> __sock_sendmsg(), in a follow-up patch.
Yeah, likely so. Thanks Paolo, we'll take a look
--
Pavel Begunkov
Powered by blists - more mailing lists