netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Herbert <tom@quantonium.net>, davem@davemloft.net
Cc: netdev@vger.kernel.org, rohit@quantonium.net,
	jchapman@katalix.com, g.nault@alphalink.fr
Subject: Re: [PATCH v2 net-next 1/2] kcm: Only allow TCP sockets to be attached to a KCM mux
Date: Wed, 24 Jan 2018 12:49:16 -0800	[thread overview]
Message-ID: <1516826956.3715.29.camel@gmail.com> (raw)
In-Reply-To: <20180124203541.3172-2-tom@quantonium.net>

On Wed, 2018-01-24 at 12:35 -0800, Tom Herbert wrote:
> TCP sockets for IPv4 and IPv6 that are not listeners or in closed
> stated are allowed to be attached to a KCM mux.
> 
> Fixes: ab7ac4eb9832 ("kcm: Kernel Connection Multiplexor module")
> Reported-by: syzbot+8865eaff7f9acd593945@syzkaller.appspotmail.com
> Signed-off-by: Tom Herbert <tom@quantonium.net>
> ---
>  net/kcm/kcmsock.c | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/net/kcm/kcmsock.c b/net/kcm/kcmsock.c
> index d4e98f20fc2a..7632797fb68e 100644
> --- a/net/kcm/kcmsock.c
> +++ b/net/kcm/kcmsock.c
> @@ -1387,8 +1387,13 @@ static int kcm_attach(struct socket *sock, struct socket *csock,
>  	if (!csk)
>  		return -EINVAL;
>  
> -	/* We must prevent loops or risk deadlock ! */
> -	if (csk->sk_family == PF_KCM)
> +	/* Only allow TCP sockets to be attached for now */
> +	if ((csk->sk_family != AF_INET && csk->sk_family != AF_INET6) ||
> +	    csk->sk_protocol != IPPROTO_TCP)
> +		return -EOPNOTSUPP;
> +
> +	/* Don't allow listeners or closed sockets */
> +	if (csk->sk_state == TCP_LISTEN || csk->sk_state == TCP_CLOSE)
>  		return -EOPNOTSUPP;
>  
>  	psock = kmem_cache_zalloc(kcm_psockp, GFP_KERNEL);


Reviewed-by: Eric Dumazet <edumazet@google.com>

  reply	other threads:[~2018-01-24 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 20:35 [PATCH v2 net-next 0/2] kcm: fix two syzcaller issues Tom Herbert
2018-01-24 20:35 ` [PATCH v2 net-next 1/2] kcm: Only allow TCP sockets to be attached to a KCM mux Tom Herbert
2018-01-24 20:49   ` Eric Dumazet [this message]
2018-01-24 20:35 ` [PATCH v2 net-next 2/2] kcm: Check if sk_user_data already set in kcm_attach Tom Herbert
2018-01-24 20:52   ` Eric Dumazet
2018-01-26 21:07   ` Eric Dumazet
2018-01-24 20:54 ` [PATCH v2 net-next 0/2] kcm: fix two syzcaller issues 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=1516826956.3715.29.camel@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=g.nault@alphalink.fr \
    --cc=jchapman@katalix.com \
    --cc=netdev@vger.kernel.org \
    --cc=rohit@quantonium.net \
    --cc=tom@quantonium.net \
    /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).