All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vyasevich@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-sctp@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
	Michio Honda <micchie@sfc.wide.ad.jp>
Subject: Re: [PATCH net] net: sctp: fix smatch warning in sctp_send_asconf_del_ip
Date: Tue, 10 Sep 2013 14:18:56 +0000	[thread overview]
Message-ID: <522F2A50.3070604@gmail.com> (raw)
In-Reply-To: <1378579881-27881-1-git-send-email-dborkman@redhat.com>

On 09/07/2013 02:51 PM, Daniel Borkmann wrote:
> This was originally reported in [1] and posted by Neil Horman [2], he said:
>
>    Fix up a missed null pointer check in the asconf code. If we don't find
>    a local address, but we pass in an address length of more than 1, we may
>    dereference a NULL laddr pointer. Currently this can't happen, as the only
>    users of the function pass in the value 1 as the addrcnt parameter, but
>    its not hot path, and it doesn't hurt to check for NULL should that ever
>    be the case.
>
> The callpath from sctp_asconf_mgmt() looks okay. But this could be triggered
> from sctp_setsockopt_bindx() call with SCTP_BINDX_REM_ADDR and addrcnt > 1
> while passing all possible addresses from the bind list to SCTP_BINDX_REM_ADDR
> so that we do *not* find a single address in the association's bind address
> list that is not in the packed array of addresses. If this happens when we
> have an established association with ASCONF-capable peers, then we could get
> a NULL pointer dereference as we only check for laddr = NULL && addrcnt = 1
> and call later sctp_make_asconf_update_ip() with NULL laddr.
>
> BUT: this actually won't happen as sctp_bindx_rem() will catch such a case
> and return with an error earlier. As this is incredably unintuitive and error
> prone, add a check to catch at least future bugs here. As Neil says, its not
> hot path. Introduced by 8a07eb0a5 ("sctp: Add ASCONF operation on the
> single-homed host").
>
>   [1] http://www.spinics.net/lists/linux-sctp/msg02132.html
>   [2] http://www.spinics.net/lists/linux-sctp/msg02133.html
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
> Cc: Michio Honda <micchie@sfc.wide.ad.jp>

Acked-by: Vlad Yasevich <vyasevich@gmail.com>

-vlad

> ---
>   net/sctp/socket.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 5462bbb..911b71b 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -806,6 +806,9 @@ static int sctp_send_asconf_del_ip(struct sock		*sk,
>   			goto skip_mkasconf;
>   		}
>
> +		if (laddr = NULL)
> +			return -EINVAL;
> +
>   		/* We do not need RCU protection throughout this loop
>   		 * because this is done under a socket lock from the
>   		 * setsockopt call.
>


WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevich@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-sctp@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
	Michio Honda <micchie@sfc.wide.ad.jp>
Subject: Re: [PATCH net] net: sctp: fix smatch warning in sctp_send_asconf_del_ip
Date: Tue, 10 Sep 2013 10:18:56 -0400	[thread overview]
Message-ID: <522F2A50.3070604@gmail.com> (raw)
In-Reply-To: <1378579881-27881-1-git-send-email-dborkman@redhat.com>

On 09/07/2013 02:51 PM, Daniel Borkmann wrote:
> This was originally reported in [1] and posted by Neil Horman [2], he said:
>
>    Fix up a missed null pointer check in the asconf code. If we don't find
>    a local address, but we pass in an address length of more than 1, we may
>    dereference a NULL laddr pointer. Currently this can't happen, as the only
>    users of the function pass in the value 1 as the addrcnt parameter, but
>    its not hot path, and it doesn't hurt to check for NULL should that ever
>    be the case.
>
> The callpath from sctp_asconf_mgmt() looks okay. But this could be triggered
> from sctp_setsockopt_bindx() call with SCTP_BINDX_REM_ADDR and addrcnt > 1
> while passing all possible addresses from the bind list to SCTP_BINDX_REM_ADDR
> so that we do *not* find a single address in the association's bind address
> list that is not in the packed array of addresses. If this happens when we
> have an established association with ASCONF-capable peers, then we could get
> a NULL pointer dereference as we only check for laddr == NULL && addrcnt == 1
> and call later sctp_make_asconf_update_ip() with NULL laddr.
>
> BUT: this actually won't happen as sctp_bindx_rem() will catch such a case
> and return with an error earlier. As this is incredably unintuitive and error
> prone, add a check to catch at least future bugs here. As Neil says, its not
> hot path. Introduced by 8a07eb0a5 ("sctp: Add ASCONF operation on the
> single-homed host").
>
>   [1] http://www.spinics.net/lists/linux-sctp/msg02132.html
>   [2] http://www.spinics.net/lists/linux-sctp/msg02133.html
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
> Cc: Michio Honda <micchie@sfc.wide.ad.jp>

Acked-by: Vlad Yasevich <vyasevich@gmail.com>

-vlad

> ---
>   net/sctp/socket.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 5462bbb..911b71b 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -806,6 +806,9 @@ static int sctp_send_asconf_del_ip(struct sock		*sk,
>   			goto skip_mkasconf;
>   		}
>
> +		if (laddr == NULL)
> +			return -EINVAL;
> +
>   		/* We do not need RCU protection throughout this loop
>   		 * because this is done under a socket lock from the
>   		 * setsockopt call.
>

  parent reply	other threads:[~2013-09-10 14:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 18:51 [PATCH net] net: sctp: fix smatch warning in sctp_send_asconf_del_ip Daniel Borkmann
2013-09-07 18:51 ` Daniel Borkmann
2013-09-07 19:40 ` Michio Honda
2013-09-07 19:40   ` Michio Honda
2013-09-07 20:11   ` Neil Horman
2013-09-07 20:11     ` Neil Horman
2013-09-07 20:19     ` Michio Honda
2013-09-07 20:19       ` Michio Honda
2013-09-07 20:19   ` Daniel Borkmann
2013-09-07 20:19     ` Daniel Borkmann
2013-09-07 20:21     ` Michio Honda
2013-09-07 20:21       ` Michio Honda
2013-09-07 20:12 ` Neil Horman
2013-09-07 20:12   ` Neil Horman
2013-09-10 14:18 ` Vlad Yasevich [this message]
2013-09-10 14:18   ` Vlad Yasevich
2013-09-11 20:14 ` David Miller
2013-09-11 20:14   ` 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=522F2A50.3070604@gmail.com \
    --to=vyasevich@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=linux-sctp@vger.kernel.org \
    --cc=micchie@sfc.wide.ad.jp \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.