syzbot


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

Status: auto-closed as invalid on 2019/02/22 14:33
First crash: 2313d, last: 2078d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 KASAN: stack-out-of-bounds Read in unwind_next_frame C 1039 412d 1671d 0/1 upstream: reported C repro on 2019/09/18 00:47
android-54 KASAN: stack-out-of-bounds Read in unwind_next_frame C 49 1019d 1523d 0/2 auto-obsoleted due to no activity on 2023/04/20 07:24
linux-4.19 KASAN: stack-out-of-bounds Read in unwind_next_frame C error 525 424d 1510d 0/1 upstream: reported C repro on 2020/02/26 18:51
upstream KASAN: stack-out-of-bounds Read in unwind_next_frame kernel C 929 390d 2126d 0/26 closed as dup on 2018/06/20 07:51
android-414 KASAN: stack-out-of-bounds Read in unwind_next_frame C 2192 1594d 1831d 0/1 public: reported C repro on 2019/04/11 00:00

Sample crash report:
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=16765 comm=syz-executor0
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=16765 comm=syz-executor0
==================================================================
BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0xcd/0xe0 arch/x86/kernel/unwind_frame.c:51
Read of size 8 at addr ffff8801d91a7de0 by task syz-executor0/16808

CPU: 0 PID: 16808 Comm: syz-executor0 Not tainted 4.9.102-gd054505 #34
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
 ffff8801982576d0 ffffffff81eb3489 ffffea00076469c0 ffff8801d91a7de0
 0000000000000000 ffff8801d91a7de0 ffff8801cdb59b40 ffff880198257708
 ffffffff815676bb ffff8801d91a7de0 0000000000000008 0000000000000000
Call Trace:
 [<ffffffff81eb3489>] __dump_stack lib/dump_stack.c:15 [inline]
 [<ffffffff81eb3489>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
 [<ffffffff815676bb>] print_address_description+0x6c/0x234 mm/kasan/report.c:256
 [<ffffffff81567ac5>] kasan_report_error mm/kasan/report.c:355 [inline]
 [<ffffffff81567ac5>] kasan_report.cold.6+0x242/0x2fe mm/kasan/report.c:412
 [<ffffffff8153b744>] __asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:433
 [<ffffffff810d2e5d>] unwind_next_frame+0xcd/0xe0 arch/x86/kernel/unwind_frame.c:51
 [<ffffffff8107b94d>] __save_stack_trace+0x7d/0xf0 arch/x86/kernel/stacktrace.c:42
 [<ffffffff8107ba28>] save_stack_trace_tsk+0x48/0x70 arch/x86/kernel/stacktrace.c:71
 [<ffffffff816d75e8>] proc_pid_stack+0x148/0x220 fs/proc/base.c:467
 [<ffffffff816d8a8d>] proc_single_show+0xfd/0x170 fs/proc/base.c:769
 [<ffffffff815e9c23>] traverse+0x363/0x920 fs/seq_file.c:124
 [<ffffffff815ed529>] seq_read+0xd19/0x12e0 fs/seq_file.c:195
 [<ffffffff8156ef45>] do_loop_readv_writev.part.18+0xd5/0x280 fs/read_write.c:718
 [<ffffffff81572e95>] do_loop_readv_writev fs/read_write.c:707 [inline]
 [<ffffffff81572e95>] do_readv_writev+0x565/0x7a0 fs/read_write.c:873
 [<ffffffff81573154>] vfs_readv+0x84/0xc0 fs/read_write.c:897
 [<ffffffff81573587>] do_preadv+0x197/0x240 fs/read_write.c:974
 [<ffffffff81576b40>] SYSC_preadv fs/read_write.c:1024 [inline]
 [<ffffffff81576b40>] SyS_preadv+0x30/0x40 fs/read_write.c:1019
 [<ffffffff81006316>] do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282
 [<ffffffff839f78d3>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb

The buggy address belongs to the page:
page:ffffea00076469c0 count:0 mapcount:0 mapping:          (null) index:0x0
flags: 0x8000000000000000()
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8801d91a7c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8801d91a7d00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8801d91a7d80: 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f2
                                                       ^
 ffff8801d91a7e00: f2 f2 f2 f2 f2 f2 00 f2 f2 f2 f2 f2 f2 f2 00 00
 ffff8801d91a7e80: f2 f2 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/05/23 18:29 https://android.googlesource.com/kernel/common android-4.9 d054505522c4 f48c20b8 .config console log report ci-android-49-kasan-gce
2017/12/17 07:22 https://android.googlesource.com/kernel/common android-4.9 3f1d77ca5f8f b6f0c91b .config console log report ci-android-49-kasan-gce
2017/12/15 05:29 https://android.googlesource.com/kernel/common android-4.9 3f1d77ca5f8f ac20b98c .config console log report ci-android-49-kasan-gce
2018/08/07 07:25 https://android.googlesource.com/kernel/common android-4.9 47b77b8d01c4 1beb8136 .config console log report ci-android-49-kasan-gce-386
2018/06/04 13:52 https://android.googlesource.com/kernel/common android-4.9 d7e64f8022e4 6cbe7c26 .config console log report ci-android-49-kasan-gce-386
* Struck through repros no longer work on HEAD.