syzbot


KASAN: stack-out-of-bounds Read in check_stack_object

Status: closed as dup on 2019/01/06 15:44
Subsystems: hardening mm
[Documentation on labels]
Reported-by: syzbot+05fc3a636f5ee8830a99@syzkaller.appspotmail.com
First crash: 1963d, last: 1953d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
kernel panic: stack is corrupted in udp4_lib_lookup2 net 11 1968d 1965d
Discussions (1)
Title Replies (including bot) Last reply
KASAN: stack-out-of-bounds Read in check_stack_object 3 (4) 2019/01/06 15:44

Sample crash report:
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(current->hardirq_context)
------------[ cut here ]------------
Bad or missing usercopy whitelist? Kernel memory overwrite attempt detected to SLAB object 'task_struct' (offset 912, size 2)!
==================================================================
BUG: KASAN: stack-out-of-bounds in task_stack_page include/linux/sched/task_stack.h:21 [inline]
BUG: KASAN: stack-out-of-bounds in check_stack_object+0x14e/0x160 mm/usercopy.c:39
Read of size 8 at addr ffff8880a9464258 by task /-1455013312

CPU: 0 PID: -1455013312 Comm:  Not tainted 5.0.0-rc2+ #27
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:

Allocated by task 2677653696:
BUG: unable to handle kernel paging request at ffffffff8cf149c0
#PF error: [normal kernel read fault]
PGD 9874067 P4D 9874067 PUD 9875063 PMD 0 
Thread overran stack, or stack corrupted
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: -1455013312 Comm:  Not tainted 5.0.0-rc2+ #27
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:depot_fetch_stack+0x10/0x30 lib/stackdepot.c:202
Code: c6 8f 22 fe e9 20 fe ff ff 48 89 df e8 b9 8f 22 fe e9 f1 fd ff ff 90 90 90 90 89 f8 c1 ef 11 25 ff ff 1f 00 81 e7 f0 3f 00 00 <48> 03 3c c5 c0 05 f5 8b 8b 47 0c 48 83 c7 18 c7 46 10 00 00 00 00
RSP: 0018:ffff8880a9463fb8 EFLAGS: 00010006
RAX: 00000000001f8880 RBX: ffff8880a9465a04 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880a9463fc0 RDI: 0000000000003ff0
RBP: ffff8880a9463fe8 R08: 000000000000001d R09: ffffed1015cc3ef9
R10: ffffed1015cc3ef8 R11: ffff8880ae61f7c7 R12: ffffea0002a51900
R13: ffff8880a9464258 R14: ffff88821bc407c0 R15: ffff8880a9465a00
FS:  0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff8cf149c0 CR3: 0000000094bbf000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Modules linked in:
WARNING: CPU: 0 PID: -1455013312 at kernel/rcu/tree_plugin.h:414 __rcu_read_lock+0x75/0x90 kernel/rcu/tree_plugin.h:416

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/01/15 13:23 upstream fe76fc6aaf53 ebacf5cb .config console log report syz ci-upstream-kasan-gce-selinux-root
2019/01/05 11:44 upstream 3fed6ae4b027 53be0a37 .config console log report syz ci-upstream-kasan-gce-386
* Struck through repros no longer work on HEAD.