From: Dmitry Vyukov <dvyukov@google.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: syzbot <syzbot+999bca54de2ee169c021@syzkaller.appspotmail.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
syzkaller-bugs@googlegroups.com,
"Thomas Gleixner" <tglx@linutronix.de>,
netdev <netdev@vger.kernel.org>
Subject: Re: KASAN: use-after-free Read in tick_sched_handle (3)
Date: Mon, 19 Nov 2018 20:42:26 -0800 [thread overview]
Message-ID: <CACT4Y+b1Eq1eXcHJR4tVyn1746pBCNqie8yapuqM3+ry3wJX4g@mail.gmail.com> (raw)
In-Reply-To: <20181120041041.GA3398@lerouge>
On Mon, Nov 19, 2018 at 8:10 PM, Frederic Weisbecker
<frederic@kernel.org> wrote:
> On Mon, Nov 19, 2018 at 01:39:02PM -0800, syzbot wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit: bae4e109837b mlxsw: spectrum: Expose discard counters via ..
>> git tree: net-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=11b5e77b400000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
>> dashboard link: https://syzkaller.appspot.com/bug?extid=999bca54de2ee169c021
>> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b7d093400000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1487a225400000
>>
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+999bca54de2ee169c021@syzkaller.appspotmail.com
>>
>> IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
>> IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
>> 8021q: adding VLAN 0 to HW filter on device team0
>> ==================================================================
>> kasan: CONFIG_KASAN_INLINE enabled
>> BUG: KASAN: use-after-free in tick_sched_handle+0x16c/0x180
>> kernel/time/tick-sched.c:164
>
> So tick_sched_timer() -> tick_sched_handle() is passed regs returned by
> get_irq_regs() that seem to be junk.
>
> Those regs should come from smp_apic_timer_interrupt().
>
> Thoughts?
Looking at the reproducer it looks like some memory corruption in
networking stack. +netdev
next prev parent reply other threads:[~2018-11-20 4:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 21:39 KASAN: use-after-free Read in tick_sched_handle (3) syzbot
2018-11-20 4:10 ` Frederic Weisbecker
2018-11-20 4:42 ` Dmitry Vyukov [this message]
2019-11-07 13:42 ` syzbot
2019-11-08 12:51 ` Stefano Brivio
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+b1Eq1eXcHJR4tVyn1746pBCNqie8yapuqM3+ry3wJX4g@mail.gmail.com \
--to=dvyukov@google.com \
--cc=frederic@kernel.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+999bca54de2ee169c021@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.