From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932559AbdDSBJG (ORCPT ); Tue, 18 Apr 2017 21:09:06 -0400 Received: from mail-pf0-f181.google.com ([209.85.192.181]:35108 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758849AbdDSBJD (ORCPT ); Tue, 18 Apr 2017 21:09:03 -0400 MIME-Version: 1.0 In-Reply-To: <732d29dc-0240-cd1a-6973-5d14636ceaee@cumulusnetworks.com> References: <2b60b1b8-4766-0e36-f6fb-79914bf1925d@cumulusnetworks.com> <328b1fa7-2d97-6ae3-3b87-e33a0d564ad9@cumulusnetworks.com> <2270c1ca-9481-60c1-9c29-87669223bded@cumulusnetworks.com> <732d29dc-0240-cd1a-6973-5d14636ceaee@cumulusnetworks.com> From: Andrey Konovalov Date: Wed, 19 Apr 2017 03:09:01 +0200 Message-ID: Subject: Re: net: heap out-of-bounds in fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone To: David Ahern Cc: Dmitry Vyukov , Eric Dumazet , Mahesh Bandewar , Eric Dumazet , David Miller , Alexey Kuznetsov , James Morris , Hideaki YOSHIFUJI , Patrick McHardy , netdev , LKML , Cong Wang , syzkaller Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 19, 2017 at 1:20 AM, David Ahern wrote: > On 4/18/17 2:43 PM, Andrey Konovalov wrote: >> I've finally managed to reproduce one of the crashes on commit >> 4f7d029b9bf009fbee76bb10c0c4351a1870d2f3 (4.11-rc7). >> >> I'm not sure if this bug has the same root cause as the first one >> reported in this thread, but it definitely has to do with ipv6 >> routing. >> >> C reproducer, syzkaller program and my .config are attached. Just FYI, the reproducer uses interface number 9 inside a user namespace, which is apparently ip6gre0. 1: lo: mtu 65536 qdisc noop state DOWN mode DEFAULT qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: mtu 1476 qdisc noop state DOWN mode DEFAULT qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: mtu 1462 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: ip_vti0@NONE: mtu 1332 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 6: ip6_vti0@NONE: mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 link/tunnel6 :: brd :: 7: sit0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 8: ip6tnl0@NONE: mtu 1452 qdisc noop state DOWN mode DEFAULT qlen 1000 link/tunnel6 :: brd :: 9: ip6gre0@NONE: mtu 1448 qdisc noop state DOWN mode DEFAULT qlen 1000 link/[823] 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 >> >> Thanks! >> >> kasan: CONFIG_KASAN_INLINE enabled >> kasan: GPF could be caused by NULL-ptr deref or user memory access >> general protection fault: 0000 [#1] SMP KASAN >> Modules linked in: >> CPU: 1 PID: 4035 Comm: a.out Not tainted 4.11.0-rc7+ #250 >> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 >> task: ffff880069809600 task.stack: ffff880062dc8000 >> RIP: 0010:ip6_rt_cache_alloc+0xa6/0x560 net/ipv6/route.c:975 > > From a quick glance seems to be a different bug than Dmitry's. It might be. >