From: Casey Schaufler <casey@schaufler-ca.com>
To: Anton Blanchard <anton@samba.org>
Cc: penguin-kernel@I-love.SAKURA.ne.jp, davem@davemloft.net,
eparis@parisplace.org, mjt@tls.msk.ru, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH 3/3] net: Fix security_socket_sendmsg() bypass problem.
Date: Thu, 04 Aug 2011 17:38:43 -0700 [thread overview]
Message-ID: <4E3B3B93.3060803@schaufler-ca.com> (raw)
In-Reply-To: <20110805000822.408914956@samba.org>
On 8/4/2011 5:07 PM, Anton Blanchard wrote:
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
>
> The sendmmsg() introduced by commit 228e548e "net: Add sendmmsg socket system
> call" is capable of sending to multiple different destination addresses.
>
> SMACK is using destination's address for checking sendmsg() permission.
> However, security_socket_sendmsg() is called for only once even if multiple
> different destination addresses are passed to sendmmsg().
>
> Therefore, we need to call security_socket_sendmsg() for each destination
> address rather than only the first destination address.
>
> Since calling security_socket_sendmsg() every time when only single destination
> address was passed to sendmmsg() is a waste of time, omit calling
> security_socket_sendmsg() unless destination address of previous datagram and
> that of current datagram differs.
Thank you.
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Acked-off: Anton Blanchard <anton@samba.org>
> Cc: stable <stable@kernel.org> [3.0+]
> ---
>
> Index: linux-net/net/socket.c
> ===================================================================
> --- linux-net.orig/net/socket.c 2011-08-05 09:31:27.000000000 +1000
> +++ linux-net/net/socket.c 2011-08-05 09:32:46.146436405 +1000
> @@ -1871,8 +1871,14 @@ SYSCALL_DEFINE2(shutdown, int, fd, int,
> #define COMPAT_NAMELEN(msg) COMPAT_MSG(msg, msg_namelen)
> #define COMPAT_FLAGS(msg) COMPAT_MSG(msg, msg_flags)
>
> +struct used_address {
> + struct sockaddr_storage name;
> + unsigned int name_len;
> +};
> +
> static int __sys_sendmsg(struct socket *sock, struct msghdr __user *msg,
> - struct msghdr *msg_sys, unsigned flags, int nosec)
> + struct msghdr *msg_sys, unsigned flags,
> + struct used_address *used_address)
> {
> struct compat_msghdr __user *msg_compat =
> (struct compat_msghdr __user *)msg;
> @@ -1953,8 +1959,28 @@ static int __sys_sendmsg(struct socket *
>
> if (sock->file->f_flags & O_NONBLOCK)
> msg_sys->msg_flags |= MSG_DONTWAIT;
> - err = (nosec ? sock_sendmsg_nosec : sock_sendmsg)(sock, msg_sys,
> - total_len);
> + /*
> + * If this is sendmmsg() and current destination address is same as
> + * previously succeeded address, omit asking LSM's decision.
> + * used_address->name_len is initialized to UINT_MAX so that the first
> + * destination address never matches.
> + */
> + if (used_address && used_address->name_len == msg_sys->msg_namelen &&
> + !memcmp(&used_address->name, msg->msg_name,
> + used_address->name_len)) {
> + err = sock_sendmsg_nosec(sock, msg_sys, total_len);
> + goto out_freectl;
> + }
> + err = sock_sendmsg(sock, msg_sys, total_len);
> + /*
> + * If this is sendmmsg() and sending to current destination address was
> + * successful, remember it.
> + */
> + if (used_address && err >= 0) {
> + used_address->name_len = msg_sys->msg_namelen;
> + memcpy(&used_address->name, msg->msg_name,
> + used_address->name_len);
> + }
>
> out_freectl:
> if (ctl_buf != ctl)
> @@ -1979,7 +2005,7 @@ SYSCALL_DEFINE3(sendmsg, int, fd, struct
> if (!sock)
> goto out;
>
> - err = __sys_sendmsg(sock, msg, &msg_sys, flags, 0);
> + err = __sys_sendmsg(sock, msg, &msg_sys, flags, NULL);
>
> fput_light(sock->file, fput_needed);
> out:
> @@ -1998,6 +2024,7 @@ int __sys_sendmmsg(int fd, struct mmsghd
> struct mmsghdr __user *entry;
> struct compat_mmsghdr __user *compat_entry;
> struct msghdr msg_sys;
> + struct used_address used_address;
>
> if (vlen > UIO_MAXIOV)
> vlen = UIO_MAXIOV;
> @@ -2008,24 +2035,22 @@ int __sys_sendmmsg(int fd, struct mmsghd
> if (!sock)
> return err;
>
> + used_address.name_len = UINT_MAX;
> entry = mmsg;
> compat_entry = (struct compat_mmsghdr __user *)mmsg;
> err = 0;
>
> while (datagrams < vlen) {
> - /*
> - * No need to ask LSM for more than the first datagram.
> - */
> if (MSG_CMSG_COMPAT & flags) {
> err = __sys_sendmsg(sock, (struct msghdr __user *)compat_entry,
> - &msg_sys, flags, datagrams);
> + &msg_sys, flags, &used_address);
> if (err < 0)
> break;
> err = __put_user(err, &compat_entry->msg_len);
> ++compat_entry;
> } else {
> err = __sys_sendmsg(sock, (struct msghdr __user *)entry,
> - &msg_sys, flags, datagrams);
> + &msg_sys, flags, &used_address);
> if (err < 0)
> break;
> err = put_user(err, &entry->msg_len);
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-08-05 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 0:07 [PATCH 0/3] sendmmsg fixes Anton Blanchard
2011-08-05 0:07 ` [PATCH 1/3] net: sendmmsg should only return an error if no messages were sent Anton Blanchard
2011-08-05 3:57 ` Tetsuo Handa
2011-08-05 8:20 ` Steven Whitehouse
2011-08-05 14:40 ` Arnaldo Carvalho de Melo
2011-08-05 0:07 ` [PATCH 2/3] net: Cap number of elements for sendmmsg Anton Blanchard
2011-08-05 4:29 ` Tetsuo Handa
2011-08-05 4:46 ` Anton Blanchard
2011-08-05 5:50 ` Tetsuo Handa
2011-08-05 0:07 ` [PATCH 3/3] net: Fix security_socket_sendmsg() bypass problem Anton Blanchard
2011-08-05 0:38 ` Casey Schaufler [this message]
2011-08-05 10:31 ` [PATCH 0/3] sendmmsg fixes David Miller
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=4E3B3B93.3060803@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=eparis@parisplace.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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;
as well as URLs for NNTP newsgroup(s).