From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+bd36b7dd9330f67037ab@syzkaller.appspotmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, Qian Cai <cai@lca.pw>,
Chris von Recklinghausen <crecklin@redhat.com>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-scope Read in corrupted
Date: Tue, 15 Jan 2019 08:25:51 +0100 [thread overview]
Message-ID: <CACT4Y+Zj0h69KdTKD8N7bcpJF4AMyDK0WGEQ8uueL5Nf3DC1YQ@mail.gmail.com> (raw)
In-Reply-To: <000000000000f49537057f77cb00@google.com>
On Tue, Jan 15, 2019 at 5:43 AM syzbot
<syzbot+bd36b7dd9330f67037ab@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 1bdbe2274920 Merge tag 'vfio-v5.0-rc2' of git://github.com..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1519d39f400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=edf1c3031097c304
> dashboard link: https://syzkaller.appspot.com/bug?extid=bd36b7dd9330f67037ab
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fce14f400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110b2017400000
Based on the reproducer this is:
#syz dup: kernel panic: stack is corrupted in udp4_lib_lookup2
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+bd36b7dd9330f67037ab@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: use-after-scope in debug_lockdep_rcu_enabled.part.0+0x50/0x60
> kernel/rcu/update.c:249
> Read of size 4 at addr ffff8880a945eabc by task
> `9������#�( �����<����� k�������E�����>9h��������A/-2122188634
>
> CPU: 0 PID: -2122188634 Comm: ��E�������������O2� Not tainted 5.0.0-rc1+
> #19
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> ------------[ cut here ]------------
> Bad or missing usercopy whitelist? Kernel memory overwrite attempt detected
> to SLAB object 'task_struct' (offset 1344, size 8)!
> WARNING: CPU: 0 PID: -1455036288 at mm/usercopy.c:78
> usercopy_warn+0xeb/0x110 mm/usercopy.c:78
> Kernel panic - not syncing: panic_on_warn set ...
> CPU: 0 PID: -1455036288 Comm: ��E�������������O2� Not tainted 5.0.0-rc1+
> #19
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
> Kernel Offset: disabled
> Rebooting in 86400 seconds..
>
>
> ---
> This bug is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
> syzbot.
> syzbot can test patches for this bug, for details see:
> https://goo.gl/tpsmEJ#testing-patches
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/000000000000f49537057f77cb00%40google.com.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2019-01-15 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 4:43 syzbot
2019-01-15 4:43 ` syzbot
2019-01-15 7:25 ` Dmitry Vyukov [this message]
2019-01-15 7:25 ` 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+Zj0h69KdTKD8N7bcpJF4AMyDK0WGEQ8uueL5Nf3DC1YQ@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=crecklin@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+bd36b7dd9330f67037ab@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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