public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
	linux-sctp@vger.kernel.org, davem@davemloft.net,
	Neil Horman <nhorman@tuxdriver.com>,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH net] sctp: not bind the socket in sctp_connect
Date: Thu, 27 Jun 2019 19:32:36 -0300	[thread overview]
Message-ID: <20190627223236.GB2747@localhost.localdomain> (raw)
In-Reply-To: <35a0e4f6ca68185117c6e5517d8ac924cc2f9d05.1561537899.git.lucien.xin@gmail.com>

On Wed, Jun 26, 2019 at 04:31:39PM +0800, Xin Long wrote:
> Now when sctp_connect() is called with a wrong sa_family, it binds
> to a port but doesn't set bp->port, then sctp_get_af_specific will
> return NULL and sctp_connect() returns -EINVAL.
> 
> Then if sctp_bind() is called to bind to another port, the last
> port it has bound will leak due to bp->port is NULL by then.
> 
> sctp_connect() doesn't need to bind ports, as later __sctp_connect
> will do it if bp->port is NULL. So remove it from sctp_connect().
> While at it, remove the unnecessary sockaddr.sa_family len check
> as it's already done in sctp_inet_connect.
> 
> Fixes: 644fbdeacf1d ("sctp: fix the issue that flags are ignored when using kernel_connect")
> Reported-by: syzbot+079bf326b38072f849d9@syzkaller.appspotmail.com
> Signed-off-by: Xin Long <lucien.xin@gmail.com>

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

> ---
>  net/sctp/socket.c | 24 +++---------------------
>  1 file changed, 3 insertions(+), 21 deletions(-)
> 
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 39ea0a3..f33aa9e 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -4816,35 +4816,17 @@ static int sctp_setsockopt(struct sock *sk, int level, int optname,
>  static int sctp_connect(struct sock *sk, struct sockaddr *addr,
>  			int addr_len, int flags)
>  {
> -	struct inet_sock *inet = inet_sk(sk);
>  	struct sctp_af *af;
> -	int err = 0;
> +	int err = -EINVAL;
>  
>  	lock_sock(sk);
> -
>  	pr_debug("%s: sk:%p, sockaddr:%p, addr_len:%d\n", __func__, sk,
>  		 addr, addr_len);
>  
> -	/* We may need to bind the socket. */
> -	if (!inet->inet_num) {
> -		if (sk->sk_prot->get_port(sk, 0)) {
> -			release_sock(sk);
> -			return -EAGAIN;
> -		}
> -		inet->inet_sport = htons(inet->inet_num);
> -	}
> -
>  	/* Validate addr_len before calling common connect/connectx routine. */
> -	af = addr_len < offsetofend(struct sockaddr, sa_family) ? NULL :
> -		sctp_get_af_specific(addr->sa_family);
> -	if (!af || addr_len < af->sockaddr_len) {
> -		err = -EINVAL;
> -	} else {
> -		/* Pass correct addr len to common routine (so it knows there
> -		 * is only one address being passed.
> -		 */
> +	af = sctp_get_af_specific(addr->sa_family);
> +	if (af && addr_len >= af->sockaddr_len)
>  		err = __sctp_connect(sk, addr, af->sockaddr_len, flags, NULL);
> -	}
>  
>  	release_sock(sk);
>  	return err;
> -- 
> 2.1.0
> 

  parent reply	other threads:[~2019-06-27 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26  8:31 [PATCH net] sctp: not bind the socket in sctp_connect Xin Long
2019-06-27  2:59 ` Marcelo Ricardo Leitner
2019-06-27 16:21   ` David Miller
2019-06-27 22:32 ` Marcelo Ricardo Leitner [this message]
2019-06-29 17:51 ` 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=20190627223236.GB2747@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=syzkaller-bugs@googlegroups.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