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

48 views
Skip to first unread message

syzbot

unread,
Feb 13, 2020, 1:18:12 PM2/13/20
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: a6e46563 UPSTREAM: dynamic_debug: allow to work if debugfs..
git tree: android-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=1521e2a1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=73ec4663f212c2a5
dashboard link: https://syzkaller.appspot.com/bug?extid=d82b1993705e29bb2edf
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d82b19...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x407/0x870 arch/x86/kernel/unwind_frame.c:305
Read of size 8 at addr ffff8881d639fe88 by task syz-executor.5/17331

CPU: 1 PID: 17331 Comm: syz-executor.5 Not tainted 5.4.19-syzkaller-00486-ga6e4656398da #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+0x1b0/0x228 lib/dump_stack.c:118
print_address_description+0x96/0x5d0 mm/kasan/report.c:374
__kasan_report+0x14b/0x1c0 mm/kasan/report.c:506
kasan_report+0x26/0x50 mm/kasan/common.c:634
__asan_report_load8_noabort+0x14/0x20 mm/kasan/generic_report.c:132
unwind_next_frame+0x407/0x870 arch/x86/kernel/unwind_frame.c:305
arch_stack_walk+0xb4/0xe0 arch/x86/kernel/stacktrace.c:25
stack_trace_save_tsk+0x2d5/0x470 kernel/stacktrace.c:151
proc_pid_stack+0x137/0x200 fs/proc/base.c:455
proc_single_show+0xd5/0x130 fs/proc/base.c:757
seq_read+0x4a8/0xdd0 fs/seq_file.c:229
do_loop_readv_writev fs/read_write.c:717 [inline]
do_iter_read+0x4a2/0x5b0 fs/read_write.c:938
vfs_readv fs/read_write.c:1000 [inline]
do_preadv+0x1f4/0x330 fs/read_write.c:1092
__do_sys_preadv fs/read_write.c:1142 [inline]
__se_sys_preadv fs/read_write.c:1137 [inline]
__x64_sys_preadv+0x9e/0xb0 fs/read_write.c:1137
do_syscall_64+0xc0/0x100 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45b3b9
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f22111bec78 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 00007f22111bf6d4 RCX: 000000000045b3b9
RDX: 000000000000022a RSI: 00000000200017c0 RDI: 0000000000000008
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000851 R14: 00000000004c9c95 R15: 000000000075bf2c

The buggy address belongs to the page:
page:ffffea000758e7c0 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0
raw: 8000000000000000 0000000000000000 ffffea0006561688 0000000000000000
raw: 0000000000000000 0000000000240000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff8881d639fd80: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1
ffff8881d639fe00: 00 00 00 00 00 00 00 00 00 f2 f2 f2 f2 f2 00 00
>ffff8881d639fe80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
^
ffff8881d639ff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881d639ff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


---
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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jul 14, 2020, 6:45:20 PM7/14/20
to syzkaller-a...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 22b73c73 ANDROID: GKI: set CONFIG_STATIC_USERMODEHELPER_PATH
git tree: android-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=1562086f100000
kernel config: https://syzkaller.appspot.com/x/.config?x=8ca81bdbe6485bee
dashboard link: https://syzkaller.appspot.com/bug?extid=d82b1993705e29bb2edf
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13195700900000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d82b19...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: stack-out-of-bounds in get_reg arch/x86/kernel/unwind_orc.c:406 [inline]
BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1949/0x2330 arch/x86/kernel/unwind_orc.c:573
Read of size 8 at addr ffff8881c8e9fe88 by task syz-executor.5/11643

CPU: 0 PID: 11643 Comm: syz-executor.5 Not tainted 5.4.51-syzkaller-00138-g22b73c7316d2 #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+0x14a/0x1ce lib/dump_stack.c:118
print_address_description+0x93/0x620 mm/kasan/report.c:374
__kasan_report+0x16d/0x1e0 mm/kasan/report.c:506
kasan_report+0x36/0x60 mm/kasan/common.c:634
get_reg arch/x86/kernel/unwind_orc.c:406 [inline]
unwind_next_frame+0x1949/0x2330 arch/x86/kernel/unwind_orc.c:573
arch_stack_walk+0xf4/0x120 arch/x86/kernel/stacktrace.c:25
stack_trace_save_tsk+0x2e7/0x490 kernel/stacktrace.c:151
proc_pid_stack+0x12f/0x1f0 fs/proc/base.c:455
proc_single_show+0xd3/0x130 fs/proc/base.c:757
seq_read+0x4aa/0xd30 fs/seq_file.c:229
do_loop_readv_writev fs/read_write.c:717 [inline]
do_iter_read+0x43b/0x550 fs/read_write.c:938
vfs_readv fs/read_write.c:1000 [inline]
do_preadv+0x213/0x350 fs/read_write.c:1092
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45cba9
Code: 8d b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 5b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f478ad48c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 00000000004fc3c0 RCX: 000000000045cba9
RDX: 00000000000001a1 RSI: 00000000200017c0 RDI: 0000000000000006
RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000089b R14: 00000000004cb8cc R15: 00007f478ad496d4

The buggy address belongs to the page:
page:ffffea000723a7c0 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0
flags: 0x8000000000000000()
raw: 8000000000000000 0000000000000000 ffffea000723a7c8 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff8881c8e9fd80: 00 00 00 00 f1 f1 f1 f1 00 00 f3 f3 00 00 00 00
ffff8881c8e9fe00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881c8e9fe80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
^
ffff8881c8e9ff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881c8e9ff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

syzbot

unread,
Jan 27, 2021, 5:59:17 AM1/27/21
to syzkaller-a...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 3bd26bb0 BACKPORT: arm64: perf: Support new DT compatibles
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=129e2ff0d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a0d2c3d63b61293f
dashboard link: https://syzkaller.appspot.com/bug?extid=d82b1993705e29bb2edf
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b3588cd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=118445b4d00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d82b19...@syzkaller.appspotmail.com

BUG: KASAN: stack-out-of-bounds in deref_stack_regs arch/x86/kernel/unwind_orc.c:360 [inline]
BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x133f/0x1f30 arch/x86/kernel/unwind_orc.c:534
Read of size 8 at addr ffff8881d08c79b8 by task syz-executor158/916

CPU: 0 PID: 916 Comm: syz-executor158 Not tainted 5.4.92-syzkaller-00492-g3bd26bb0aaee #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+0x1dd/0x24e lib/dump_stack.c:118
print_address_description+0x96/0x640 mm/kasan/report.c:374
__kasan_report+0x177/0x1f0 mm/kasan/report.c:506
kasan_report+0x30/0x60 mm/kasan/common.c:634
deref_stack_regs arch/x86/kernel/unwind_orc.c:360 [inline]
unwind_next_frame+0x133f/0x1f30 arch/x86/kernel/unwind_orc.c:534
arch_stack_walk+0x114/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save_tsk+0x17c/0x270 kernel/stacktrace.c:151
proc_pid_stack+0x12f/0x1f0 fs/proc/base.c:455
proc_single_show+0xd3/0x120 fs/proc/base.c:757
seq_read+0x4aa/0xd30 fs/seq_file.c:229
do_loop_readv_writev fs/read_write.c:714 [inline]
do_iter_read+0x43b/0x550 fs/read_write.c:935
vfs_readv fs/read_write.c:997 [inline]
do_preadv+0x20d/0x350 fs/read_write.c:1089
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x447e49
Code: e8 ac e7 ff ff 48 83 c4 18 c3 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 cb 05 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fede7733d08 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 00000000006e3a18 RCX: 0000000000447e49
RDX: 00000000000001c1 RSI: 00000000200017c0 RDI: 0000000000000003
RBP: 00000000006e3a10 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006e3a1c
R13: 00007fede7733d10 R14: 00007fede7733d10 R15: 00000000004b0240

The buggy address belongs to the page:
page:ffffea00074231c0 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0
flags: 0x8000000000000000()
raw: 8000000000000000 ffffea0007322408 ffffea0007423188 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff8881d08c7880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881d08c7900: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 00
>ffff8881d08c7980: 00 f3 f3 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00
^
ffff8881d08c7a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881d08c7a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

syzbot

unread,
Apr 20, 2023, 3:24:37 AM4/20/23
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages