From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ido Schimmel Subject: Re: KASAN: use-after-free Read in fib6_ifup (2) Date: Fri, 19 Jan 2018 15:19:50 +0200 Message-ID: <20180119131949.GA19786@splinter> References: <001a11444e645c220905631ac3dc@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org, weiwan@google.com To: syzbot Return-path: Received: from out1-smtp.messagingengine.com ([66.111.4.25]:42713 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753332AbeASNTx (ORCPT ); Fri, 19 Jan 2018 08:19:53 -0500 Content-Disposition: inline In-Reply-To: <001a11444e645c220905631ac3dc@google.com> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Jan 18, 2018 at 09:58:01PM -0800, syzbot wrote: > Hello, > > syzbot hit the following crash on net-next commit > 564737f981fb4b4b3266901508bb9b90d9d43de8 > > So far this crash happened 18 times on mmots, net-next. > C reproducer is attached. > syzkaller reproducer is attached. > Raw console output is attached. > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached. > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+22b2e8ffdc35d97b5942@syzkaller.appspotmail.com > It will help syzbot understand when the bug is fixed. See footer for > details. > If you forward the report, please keep this part and the footer. > > device lo entered promiscuous mode > device lo left promiscuous mode > device lo entered promiscuous mode > ================================================================== > BUG: KASAN: use-after-free in fib6_ifup+0x212/0x220 net/ipv6/route.c:3573 After applying Wei's recent commit 7f8e6b09f32d ("ipv6: don't let tb6_root node share routes with other node") on top of net-next I can no longer reproduce the issue with the provided reproducer (repro.syz.txt). Will try to understand the exact reason for the bug before marking this as fixed.