syzbot


BUG: unable to handle kernel paging request in bpf_prog_ADDR_F

Status: upstream: reported on 2022/07/03 07:23
Reported-by: syzbot+66d306fee539916084c2@syzkaller.appspotmail.com
First crash: 125d, last: 53d

Sample crash report:
BUG: unable to handle page fault for address: ffffffffa0000d58
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD ba8f067 P4D ba8f067 PUD ba90063 PMD 169e2067 PTE 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 18149 Comm: syz-executor.0 Not tainted 5.19.0-rc8-syzkaller-00130-g8eaa1d110800 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:bpf_prog_9d4bccaf8ccaf0dc_F+0x0/0xd
Code: Unable to access opcode bytes at RIP 0xffffffffa0000d2e.
RSP: 0018:ffffc90009e7f818 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffffc90009e01000 RCX: 0000000000000000
RDX: 1ffff920013c0206 RSI: ffffc90009e01048 RDI: 00000000ffff8880
RBP: ffffc90009e7f820 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000001
R13: ffff8880252a3b00 R14: ffff888020119d80 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffa0000d2e CR3: 0000000070c1b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 bpf_dispatcher_nop_func include/linux/bpf.h:869 [inline]
 __bpf_prog_run include/linux/filter.h:628 [inline]
 bpf_prog_run include/linux/filter.h:635 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:2046 [inline]
 bpf_trace_run4+0x124/0x360 kernel/trace/bpf_trace.c:2085
 __bpf_trace_sched_switch+0x115/0x160 include/trace/events/sched.h:222
 __traceiter_sched_switch+0x68/0xb0 include/trace/events/sched.h:222
 trace_sched_switch include/trace/events/sched.h:222 [inline]
 __schedule+0x145b/0x4b50 kernel/sched/core.c:6455
 do_task_dead+0xd1/0x100 kernel/sched/core.c:6476
 do_exit+0x18d5/0x29d0 kernel/exit.c:847
 do_group_exit+0xd2/0x2f0 kernel/exit.c:925
 get_signal+0x2542/0x2600 kernel/signal.c:2857
 arch_do_signal_or_restart+0x82/0x2300 arch/x86/kernel/signal.c:869
 exit_to_user_mode_loop kernel/entry/common.c:166 [inline]
 exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:201
 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
 syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:294
 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd0d0e89279
Code: Unable to access opcode bytes at RIP 0x7fd0d0e8924f.
RSP: 002b:00007fd0d1f88168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: 0000000000000040 RBX: 00007fd0d0f9bf80 RCX: 00007fd0d0e89279
RDX: 0000000000000000 RSI: 0000000020000280 RDI: 0000000000000005
RBP: 00007fd0d0ee3189 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffca1d6264f R14: 00007fd0d1f88300 R15: 0000000000022000
 </TASK>
Modules linked in:
CR2: ffffffffa0000d58
---[ end trace 0000000000000000 ]---
RIP: 0010:bpf_prog_9d4bccaf8ccaf0dc_F+0x0/0xd
Code: Unable to access opcode bytes at RIP 0xffffffffa0000d2e.
RSP: 0018:ffffc90009e7f818 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffffc90009e01000 RCX: 0000000000000000
RDX: 1ffff920013c0206 RSI: ffffc90009e01048 RDI: 00000000ffff8880
RBP: ffffc90009e7f820 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000001
R13: ffff8880252a3b00 R14: ffff888020119d80 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffa0000d2e CR3: 0000000070c1b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (11):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-net-this-kasan-gce 2022/08/08 17:39 net 8eaa1d110800 88e3a122 .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-bpf-kasan-gce 2022/08/04 06:00 bpf 9fe2e6f39606 1c9013ac .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-net-this-kasan-gce 2022/07/27 15:26 net b5177ed92bf6 da9d0366 .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-bpf-kasan-gce 2022/07/25 23:36 bpf f946964a9f79 664c519c .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-net-this-kasan-gce 2022/07/20 12:54 net 53eb9b04560c 775344bc .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-bpf-kasan-gce 2022/06/28 13:13 bpf 179a93f74b29 ef82eb2c .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-bpf-kasan-gce 2022/06/04 08:48 bpf d08af2c46881 c8857892 .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-net-kasan-gce 2022/07/11 09:13 net-next 0076cad30135 b5765a15 .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-bpf-next-kasan-gce 2022/07/03 07:22 bpf-next b0d93b44641a 1434eec0 .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-bpf-next-kasan-gce 2022/06/25 01:13 bpf-next 395e942d34a2 a5dbd430 .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
ci-upstream-bpf-next-kasan-gce 2022/05/29 01:48 bpf-next 7e062cda7d90 a46af346 .config log report info BUG: unable to handle kernel paging request in bpf_prog_ADDR_F
* Struck through repros no longer work on HEAD.