All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Gong, Sishuai" <sishuai@purdue.edu>
Cc: David Miller <davem@davemloft.net>,
	"tparkin@katalix.com" <tparkin@katalix.com>,
	Matthias Schiffer <mschiffer@universe-factory.net>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: fix a concurrency bug in l2tp_tunnel_register()
Date: Wed, 28 Apr 2021 12:45:34 -0700	[thread overview]
Message-ID: <20210428124534.6f1d7dc4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <1F82E994-8F0B-499F-BA1A-8F1B2EEF1BF2@purdue.edu>

On Tue, 27 Apr 2021 15:04:24 +0000 Gong, Sishuai wrote:
> l2tp_tunnel_register() registers a tunnel without fully
> initializing its attribute. This can allow another kernel thread
> running l2tp_xmit_core() to access the uninitialized data and
> then cause a kernel NULL pointer dereference error, as shown below.
> 
> Thread 1    Thread 2
> //l2tp_tunnel_register()
> list_add_rcu(&tunnel->list, &pn->l2tp_tunnel_list);
>            //pppol2tp_connect()
>            tunnel = l2tp_tunnel_get(sock_net(sk), info.tunnel_id);
>            // Fetch the new tunnel
>            ...
>            //l2tp_xmit_core()
>            struct sock *sk = tunnel->sock;
>            ...
>            bh_lock_sock(sk);
>            //Null pointer error happens
> tunnel->sock = sk;
> 
> Fix this bug by initializing tunnel->sock before adding the
> tunnel into l2tp_tunnel_list.
> 
> Reviewed-by: Cong Wang <cong.wang@bytedance.com>
> Signed-off-by: Sishuai Gong <sishuai@purdue.edu>
> Reported-by: Sishuai Gong <sishuai@purdue.edu>

Thanks for the patch! Unfortunately the patch in the email is
corrupted, looks like something removed spaces at the start of 
the lines which are expected in patches, e.g.:

»       pn·=·l2tp_pernet(net);$
$
+»      sk·=·sock->sk;$

Should have been:

 »      pn·=·l2tp_pernet(net);$
 $
+»      sk·=·sock->sk;$

Could you try to resend once more with git-send-email or via 
a different mail server?

  parent reply	other threads:[~2021-04-28 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 15:04 [PATCH] net: fix a concurrency bug in l2tp_tunnel_register() Gong, Sishuai
2021-04-27 16:50 ` Tom Parkin
2021-04-28 19:45 ` Jakub Kicinski [this message]
2021-04-28 22:23   ` Jakub Kicinski
     [not found] <20210414211411.16355-1-sishuai@purdue.edu>
2021-04-15  4:10 ` Cong Wang

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=20210428124534.6f1d7dc4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=mschiffer@universe-factory.net \
    --cc=netdev@vger.kernel.org \
    --cc=sishuai@purdue.edu \
    --cc=tparkin@katalix.com \
    --cc=xiyou.wangcong@gmail.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.