From: Dmitry Vyukov <dvyukov@google.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Gerrit Renker <gerrit@erg.abdn.ac.uk>,
"David S. Miller" <davem@davemloft.net>,
dccp@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
syzkaller <syzkaller@googlegroups.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/dccp: fix use after free in tw_timer_handler()
Date: Tue, 21 Feb 2017 14:56:59 +0300 [thread overview]
Message-ID: <CACT4Y+a0uLVFHgDPi05kXsMEsraxbTOkPnK3xdZZ1_8E_vH_CQ@mail.gmail.com> (raw)
In-Reply-To: <20170221112740.661-1-aryabinin@virtuozzo.com>
On Tue, Feb 21, 2017 at 2:27 PM, Andrey Ryabinin
<aryabinin@virtuozzo.com> wrote:
> DCCP doesn't purge timewait sockets on network namespace shutdown.
> So, after net namespace destroyed we could still have an active timer
> which will trigger use after free in tw_timer_handler():
>
> BUG: KASAN: use-after-free in tw_timer_handler+0x4a/0xa0 at addr ffff88010e0d1e10
> Read of size 8 by task swapper/1/0
> Call Trace:
> __asan_load8+0x54/0x90
> tw_timer_handler+0x4a/0xa0
> call_timer_fn+0x127/0x480
> expire_timers+0x1db/0x2e0
> run_timer_softirq+0x12f/0x2a0
> __do_softirq+0x105/0x5b4
> irq_exit+0xdd/0xf0
> smp_apic_timer_interrupt+0x57/0x70
> apic_timer_interrupt+0x90/0xa0
>
> Object at ffff88010e0d1bc0, in cache net_namespace size: 6848
> Allocated:
> save_stack_trace+0x1b/0x20
> kasan_kmalloc+0xee/0x180
> kasan_slab_alloc+0x12/0x20
> kmem_cache_alloc+0x134/0x310
> copy_net_ns+0x8d/0x280
> create_new_namespaces+0x23f/0x340
> unshare_nsproxy_namespaces+0x75/0xf0
> SyS_unshare+0x299/0x4f0
> entry_SYSCALL_64_fastpath+0x18/0xad
> Freed:
> save_stack_trace+0x1b/0x20
> kasan_slab_free+0xae/0x180
> kmem_cache_free+0xb4/0x350
> net_drop_ns+0x3f/0x50
> cleanup_net+0x3df/0x450
> process_one_work+0x419/0xbb0
> worker_thread+0x92/0x850
> kthread+0x192/0x1e0
> ret_from_fork+0x2e/0x40
>
> Add .exit_batch hook to dccp_v4_ops()/dccp_v6_ops() which will purge
> timewait sockets on net namespace destruction and prevent above issue.
Aha! Thanks for tracking this down!
Queued the patch on syzkaller bots, should have the verdict in several hours.
> Reported-by: Dmitry Vyukov <dvyukov@google.com>
> Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
> ---
> net/dccp/ipv4.c | 6 ++++++
> net/dccp/ipv6.c | 6 ++++++
> 2 files changed, 12 insertions(+)
>
> diff --git a/net/dccp/ipv4.c b/net/dccp/ipv4.c
> index d859a5c..da7cb16 100644
> --- a/net/dccp/ipv4.c
> +++ b/net/dccp/ipv4.c
> @@ -1018,9 +1018,15 @@ static void __net_exit dccp_v4_exit_net(struct net *net)
> inet_ctl_sock_destroy(net->dccp.v4_ctl_sk);
> }
>
> +static void __net_exit dccp_v4_exit_batch(struct list_head *net_exit_list)
> +{
> + inet_twsk_purge(&dccp_hashinfo, &dccp_death_row, AF_INET);
> +}
> +
> static struct pernet_operations dccp_v4_ops = {
> .init = dccp_v4_init_net,
> .exit = dccp_v4_exit_net,
> + .exit_batch = dccp_v4_exit_batch,
> };
>
> static int __init dccp_v4_init(void)
> diff --git a/net/dccp/ipv6.c b/net/dccp/ipv6.c
> index c4e879c..f3d8f92 100644
> --- a/net/dccp/ipv6.c
> +++ b/net/dccp/ipv6.c
> @@ -1077,9 +1077,15 @@ static void __net_exit dccp_v6_exit_net(struct net *net)
> inet_ctl_sock_destroy(net->dccp.v6_ctl_sk);
> }
>
> +static void __net_exit dccp_v6_exit_batch(struct list_head *net_exit_list)
> +{
> + inet_twsk_purge(&dccp_hashinfo, &dccp_death_row, AF_INET6);
> +}
> +
> static struct pernet_operations dccp_v6_ops = {
> .init = dccp_v6_init_net,
> .exit = dccp_v6_exit_net,
> + .exit_batch = dccp_v6_exit_batch,
> };
>
> static int __init dccp_v6_init(void)
> --
> 2.10.2
>
next prev parent reply other threads:[~2017-02-21 11:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 10:19 net: use-after-free in tw_timer_handler Dmitry Vyukov
2017-01-23 10:23 ` Dmitry Vyukov
2017-01-24 14:28 ` Eric Dumazet
2017-01-24 15:06 ` Dmitry Vyukov
2017-01-24 15:52 ` Eric Dumazet
2017-02-08 17:36 ` Dmitry Vyukov
2017-02-08 17:58 ` Eric Dumazet
2017-02-08 18:55 ` Dmitry Vyukov
2017-02-08 19:17 ` Eric Dumazet
2017-02-08 19:32 ` Dmitry Vyukov
2017-02-14 19:38 ` Dmitry Vyukov
2017-02-21 11:27 ` [PATCH] net/dccp: fix use after free in tw_timer_handler() Andrey Ryabinin
2017-02-21 11:56 ` Dmitry Vyukov [this message]
2017-02-22 6:48 ` Dmitry Vyukov
2017-02-21 13:43 ` Arnaldo Carvalho de Melo
2017-02-21 13:53 ` Eric Dumazet
2017-02-21 18:23 ` David Miller
2017-02-22 8:59 ` Andrey Ryabinin
2017-02-21 18:23 ` David Miller
2017-02-21 18:24 ` David Miller
2017-02-22 9:35 ` Andrey Ryabinin
2017-02-22 9:35 ` [PATCH v2] " Andrey Ryabinin
2017-02-22 21:15 ` David Miller
2017-02-17 18:51 ` net: use-after-free in tw_timer_handler Cong Wang
2017-02-17 20:36 ` Dmitry Vyukov
2017-02-17 22:30 ` Cong Wang
2017-02-21 9:46 ` Dmitry Vyukov
2017-02-21 10:40 ` Dmitry Vyukov
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=CACT4Y+a0uLVFHgDPi05kXsMEsraxbTOkPnK3xdZZ1_8E_vH_CQ@mail.gmail.com \
--to=dvyukov@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=edumazet@google.com \
--cc=gerrit@erg.abdn.ac.uk \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.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).