From: Kuniyuki Iwashima <kuniyu@google.com>
To: Avi Weiss <thnkslprpt@gmail.com>
Cc: netdev@vger.kernel.org, edumazet@kernel.org, pabeni@redhat.com,
willemb@google.com, davem@davemloft.net, kuba@kernel.org,
horms@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] net: check the recvmsg LSM hook for every recvmmsg entry
Date: Sun, 1 Nov 2026 15:42:02 +0000 [thread overview]
Message-ID: <auddRPy5o927NtZH@google.com> (raw)
In-Reply-To: <edbdf4f4075565b1fb5925d7e311d6f315151a48.1793444262.git.thnkslprpt@gmail.com>
On Sat, 31 Oct 2026 13:08:41 +0200, Avi Weiss wrote:
> do_recvmmsg() passes the number of received datagrams as the nosec
> argument to ___sys_recvmsg(). After the first datagram, this bypasses
> security_socket_recvmsg() even when a later entry requests a larger
> receive buffer that would be rejected by an LSM policy.
Same question, what is the real use case ?
>
> Pass zero for both native and compat entries so each receive goes
> through the security check. Remove the first-datagram-only comment.
>
> Fixes: a2e2725541fa ("net: Introduce recvmmsg socket syscall")
Remove this.
> Signed-off-by: Avi Weiss <thnkslprpt@gmail.com>
> ---
> net/socket.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/net/socket.c b/net/socket.c
> index c2a85224ab55..fff80fbca1a8 100644
> --- a/net/socket.c
> +++ b/net/socket.c
> @@ -3057,13 +3057,10 @@ static int do_recvmmsg(int fd, struct mmsghdr __user *mmsg,
> compat_entry = (struct compat_mmsghdr __user *)mmsg;
>
> while (datagrams < vlen) {
> - /*
> - * No need to ask LSM for more than the first datagram.
> - */
> if (MSG_CMSG_COMPAT & flags) {
> err = ___sys_recvmsg(sock, (struct user_msghdr __user *)compat_entry,
> &msg_sys, flags & ~MSG_WAITFORONE,
> - datagrams);
> + 0);
> if (err < 0)
> break;
> err = put_user(err, &compat_entry->msg_len);
> @@ -3072,7 +3069,7 @@ static int do_recvmmsg(int fd, struct mmsghdr __user *mmsg,
> err = ___sys_recvmsg(sock,
> (struct user_msghdr __user *)entry,
> &msg_sys, flags & ~MSG_WAITFORONE,
> - datagrams);
> + 0);
This makes nosec dead in every path.
---
pw-bot: cr
> if (err < 0)
> break;
> err = put_user(err, &entry->msg_len);
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-11-01 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 11:08 [PATCH net 1/2] net: check the sendmsg LSM hook for every batched message Avi Weiss
2026-10-31 11:08 ` [PATCH net 2/2] net: check the recvmsg LSM hook for every recvmmsg entry Avi Weiss
2026-11-01 15:42 ` Kuniyuki Iwashima [this message]
2026-11-01 15:38 ` [PATCH net 1/2] net: check the sendmsg LSM hook for every batched message Kuniyuki Iwashima
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=auddRPy5o927NtZH@google.com \
--to=kuniyu@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thnkslprpt@gmail.com \
--cc=willemb@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®