syzbot


KASAN: use-after-scope Read in corrupted

Status: closed as dup on 2019/01/15 07:26
Subsystems: hardening mm
[Documentation on labels]
Reported-by: syzbot+bd36b7dd9330f67037ab@syzkaller.appspotmail.com
First crash: 2164d, last: 2163d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
kernel panic: stack is corrupted in udp4_lib_lookup2 net 11 2175d 2172d
Discussions (1)
Title Replies (including bot) Last reply
KASAN: use-after-scope Read in corrupted 1 (2) 2019/01/15 07:25

Sample crash report:
==================================================================
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#(<kE>9hA/-2122188634

CPU: 0 PID: -2122188634 Comm: EO2 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: EO2 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..

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/01/11 03:41 upstream 1bdbe2274920 80dde172 .config console log report syz C ci-upstream-kasan-gce-root
2019/01/12 00:37 upstream de6629eb262e c3f3344c .config console log report syz ci-upstream-kasan-gce
* Struck through repros no longer work on HEAD.