Re: KASAN: use-after-free Read in tick_sched_handle (3)

Re: KASAN: use-after-free Read in tick_sched_handle (3)

[Dmitry Vyukov]

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

Re: KASAN: use-after-free Read in tick_sched_handle (3)

[syzbot]

syzbot suspects this bug was fixed by commit:

commit bc6e019b6ee65ff4ebf3ca272f774cf6c67db669
Author: Stefano Brivio <sbrivio@redhat.com>
Date:   Thu Jan 3 20:43:34 2019 +0000

     fou: Prevent unbounded recursion in GUE error handler also with UDP-Lite

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=119c0bc2600000
start commit:   1c7fc5cb Linux 5.0-rc2
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=817708c0a0300f84
dashboard link: https://syzkaller.appspot.com/bug?extid=999bca54de2ee169c021
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12c95a30c00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11df0107400000

If the result looks correct, please mark the bug fixed by replying with:

#syz fix: fou: Prevent unbounded recursion in GUE error handler also with  
UDP-Lite

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

Re: KASAN: use-after-free Read in tick_sched_handle (3)

[Stefano Brivio]

On Thu, 07 Nov 2019 05:42:07 -0800
syzbot <syzbot+999bca54de2ee169c021@syzkaller.appspotmail.com> wrote:

> syzbot suspects this bug was fixed by commit:
> 
> commit bc6e019b6ee65ff4ebf3ca272f774cf6c67db669
> Author: Stefano Brivio <sbrivio@redhat.com>
> Date:   Thu Jan 3 20:43:34 2019 +0000
> 
>      fou: Prevent unbounded recursion in GUE error handler also with UDP-Lite
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=119c0bc2600000
> start commit:   1c7fc5cb Linux 5.0-rc2
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=817708c0a0300f84
> dashboard link: https://syzkaller.appspot.com/bug?extid=999bca54de2ee169c021
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12c95a30c00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11df0107400000
> 
> If the result looks correct, please mark the bug fixed by replying with:
> 
> #syz fix: fou: Prevent unbounded recursion in GUE error handler also with  
> UDP-Lite
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

#syz fix: fou: Prevent unbounded recursion in GUE error handler also with UDP-Lite