netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: selinux@vger.kernel.org, network dev <netdev@vger.kernel.org>,
	linux-sctp@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
	Paul Moore <paul@paul-moore.com>,
	Richard Haines <richard_c_haines@btinternet.com>
Subject: Re: [PATCH net] selinux: add the missing walk_size + len check in selinux_sctp_bind_connect
Date: Fri, 8 Mar 2019 14:08:38 -0300	[thread overview]
Message-ID: <20190308170838.GF13515@localhost.localdomain> (raw)
In-Reply-To: <1e5accb3a4a5575ada1dbdfc6e5d9e4358131f83.1552061254.git.lucien.xin@gmail.com>

On Sat, Mar 09, 2019 at 12:07:34AM +0800, Xin Long wrote:
> As does in __sctp_connect(), when checking addrs in a while loop, after
> get the addr len according to sa_family, it's necessary to do the check
> walk_size + af->sockaddr_len > addrs_size to make sure it won't access
> an out-of-bounds addr.
> 
> The same thing is needed in selinux_sctp_bind_connect(), otherwise an
> out-of-bounds issue can be triggered:
> 
>   [14548.772313] BUG: KASAN: slab-out-of-bounds in selinux_sctp_bind_connect+0x1aa/0x1f0
>   [14548.927083] Call Trace:
>   [14548.938072]  dump_stack+0x9a/0xe9
>   [14548.953015]  print_address_description+0x65/0x22e
>   [14548.996524]  kasan_report.cold.6+0x92/0x1a6
>   [14549.015335]  selinux_sctp_bind_connect+0x1aa/0x1f0
>   [14549.036947]  security_sctp_bind_connect+0x58/0x90
>   [14549.058142]  __sctp_setsockopt_connectx+0x5a/0x150 [sctp]
>   [14549.081650]  sctp_setsockopt.part.24+0x1322/0x3ce0 [sctp]
> 
> Fixes: d452930fd3b9 ("selinux: Add SCTP support")
> Reported-by: Chunyu Hu <chuhu@redhat.com>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>

Reviewed-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>

Paul, how can we get this into -stable trees? SELinux process may be
different from -net trees.

> ---
>  security/selinux/hooks.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> index f0e36c3..dac9bdb 100644
> --- a/security/selinux/hooks.c
> +++ b/security/selinux/hooks.c
> @@ -5120,6 +5120,9 @@ static int selinux_sctp_bind_connect(struct sock *sk, int optname,
>  			return -EINVAL;
>  		}
>  
> +		if (walk_size + len > addrlen)
> +			return -EINVAL;
> +
>  		err = -EINVAL;
>  		switch (optname) {
>  		/* Bind checks */
> -- 
> 2.1.0
> 

  reply	other threads:[~2019-03-08 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 16:07 [PATCH net] selinux: add the missing walk_size + len check in selinux_sctp_bind_connect Xin Long
2019-03-08 17:08 ` Marcelo Ricardo Leitner [this message]
2019-03-09  2:47   ` Paul Moore
2019-03-11 20:11     ` Paul Moore
2019-03-11 23:49       ` Marcelo Ricardo Leitner

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=20190308170838.GF13515@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=paul@paul-moore.com \
    --cc=richard_c_haines@btinternet.com \
    --cc=selinux@vger.kernel.org \
    /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).