Hello, syzbot found the following issue on: HEAD commit: 70b97111 bpf: Use hlist_add_head_rcu when linking to local.. git tree: bpf-next console output: https://syzkaller.appspot.com/x/log.txt?x=15c624ad900000 kernel config: https://syzkaller.appspot.com/x/.config?x=7e0ca96a9b6ee858 dashboard link: https://syzkaller.appspot.com/bug?extid=845923d2172947529b58 compiler: gcc (GCC) 10.1.0-syz 20200507 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10193f3b900000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168c729b900000 The issue was bisected to: commit 0a93dc1c18fd86f936bcb44f72dc044c0ea826a8 Author: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx> Date: Wed Oct 12 11:11:16 2016 +0000 [media] dvb-core: don't break long lines bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=170e18d3900000 final oops: https://syzkaller.appspot.com/x/report.txt?x=148e18d3900000 console output: https://syzkaller.appspot.com/x/log.txt?x=108e18d3900000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+845923d2172947529b58@xxxxxxxxxxxxxxxxxxxxxxxxx Fixes: 0a93dc1c18fd ("[media] dvb-core: don't break long lines") ================================================================== BUG: KASAN: vmalloc-out-of-bounds in __bpf_trace_run kernel/trace/bpf_trace.c:1937 [inline] BUG: KASAN: vmalloc-out-of-bounds in bpf_trace_run2+0x397/0x3d0 kernel/trace/bpf_trace.c:1974 Read of size 8 at addr ffffc90000e76030 by task syz-executor514/6838 CPU: 0 PID: 6838 Comm: syz-executor514 Not tainted 5.9.0-rc1-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+0x18f/0x20d lib/dump_stack.c:118 print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383 __kasan_report mm/kasan/report.c:513 [inline] kasan_report.cold+0x1f/0x37 mm/kasan/report.c:530 __bpf_trace_run kernel/trace/bpf_trace.c:1937 [inline] bpf_trace_run2+0x397/0x3d0 kernel/trace/bpf_trace.c:1974 trace_sys_enter include/trace/events/syscalls.h:18 [inline] syscall_trace_enter kernel/entry/common.c:64 [inline] syscall_enter_from_user_mode+0x22c/0x290 kernel/entry/common.c:82 do_syscall_64+0xf/0x70 arch/x86/entry/common.c:41 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x4441ba Code: 25 18 00 00 00 00 74 01 f0 48 0f b1 3d ef f9 28 00 48 39 c2 75 da f3 c3 0f 1f 84 00 00 00 00 00 48 63 ff b8 e4 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 06 f3 c3 0f 1f 40 00 48 c7 c2 d0 ff ff ff f7 RSP: 002b:00007ffeec2fd9d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e4 RAX: ffffffffffffffda RBX: 0000000000001ac2 RCX: 00000000004441ba RDX: 0000000000000000 RSI: 00007ffeec2fd9e0 RDI: 0000000000000001 RBP: 000000000000e4f7 R08: 0000000000001ab6 R09: 00000000022b5880 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004022d0 R13: 0000000000402360 R14: 0000000000000000 R15: 0000000000000000 Memory state around the buggy address: ffffc90000e75f00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffc90000e75f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 >ffffc90000e76000: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ^ ffffc90000e76080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffc90000e76100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ================================================================== --- This report 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 syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches
