syzbot


KASAN: user-memory-access Read in syscall_trace_enter

Status: auto-closed as invalid on 2020/07/23 04:01
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+08bbb3a3d0e1835855fe@syzkaller.appspotmail.com
First crash: 1434d, last: 1434d

Sample crash report:
==================================================================
BUG: KASAN: user-memory-access in syscall_trace_enter+0xbcb/0xd10 arch/x86/entry/common.c:99
Read of size 8 at addr 000000c014a3aa50 by task syz-fuzzer/7033

CPU: 0 PID: 7033 Comm: syz-fuzzer Not tainted 5.7.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x188/0x20d lib/dump_stack.c:118
 __kasan_report.cold+0x5/0x4d mm/kasan/report.c:515
 kasan_report+0x33/0x50 mm/kasan/common.c:625
 syscall_trace_enter+0xbcb/0xd10 arch/x86/entry/common.c:99
==================================================================
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 7033 Comm: syz-fuzzer Tainted: G    B             5.7.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x188/0x20d lib/dump_stack.c:118
 panic+0x2e3/0x75c kernel/panic.c:221
 end_report+0x4d/0x53 mm/kasan/report.c:103
 __kasan_report.cold+0xd/0x4d mm/kasan/report.c:518
 kasan_report+0x33/0x50 mm/kasan/common.c:625
 syscall_trace_enter+0xbcb/0xd10 arch/x86/entry/common.c:99
Shutting down cpus with NMI
Kernel Offset: disabled

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/04/24 04:00 upstream c578ddb39e56 2e44d63e .config console log report ci-upstream-kasan-gce-386
* Struck through repros no longer work on HEAD.