Hello, syzbot found the following issue on: HEAD commit: 614da38e2f7a Merge tag 'hid-for-linus-2024051401' of git:/.. git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=1429a96c980000 kernel config: https://syzkaller.appspot.com/x/.config?x=f5d2cbf33633f507 dashboard link: https://syzkaller.appspot.com/bug?extid=80cf9d55d6fd2d6a9838 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a53ae4980000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=113003d4980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/89eafb874b71/disk-614da38e.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/356000512ad9/vmlinux-614da38e.xz kernel image: https://storage.googleapis.com/syzbot-assets/839c73939115/bzImage-614da38e.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+80cf9d55d6fd2d6a9838@xxxxxxxxxxxxxxxxxxxxxxxxx ===================================================== BUG: KMSAN: uninit-value in __dev_map_hash_lookup_elem kernel/bpf/devmap.c:270 [inline] BUG: KMSAN: uninit-value in dev_map_hash_lookup_elem+0x116/0x2e0 kernel/bpf/devmap.c:803 __dev_map_hash_lookup_elem kernel/bpf/devmap.c:270 [inline] dev_map_hash_lookup_elem+0x116/0x2e0 kernel/bpf/devmap.c:803 ____bpf_map_lookup_elem kernel/bpf/helpers.c:42 [inline] bpf_map_lookup_elem+0x5c/0x80 kernel/bpf/helpers.c:38 ___bpf_prog_run+0x13fe/0xe0f0 kernel/bpf/core.c:1997 __bpf_prog_run64+0xb5/0xe0 kernel/bpf/core.c:2236 bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline] __bpf_prog_run include/linux/filter.h:657 [inline] bpf_prog_run include/linux/filter.h:664 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:2381 [inline] bpf_trace_run4+0x150/0x340 kernel/trace/bpf_trace.c:2422 __bpf_trace_sched_switch+0x37/0x50 include/trace/events/sched.h:222 trace_sched_switch include/trace/events/sched.h:222 [inline] __schedule+0x2eca/0x6bc0 kernel/sched/core.c:6743 __schedule_loop kernel/sched/core.c:6823 [inline] schedule+0x13d/0x380 kernel/sched/core.c:6838 ptrace_stop+0x8eb/0xd60 kernel/signal.c:2358 ptrace_do_notify kernel/signal.c:2395 [inline] ptrace_notify+0x234/0x320 kernel/signal.c:2407 ptrace_report_syscall include/linux/ptrace.h:415 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline] syscall_exit_work+0x14e/0x3e0 kernel/entry/common.c:173 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline] syscall_exit_to_user_mode+0x135/0x160 kernel/entry/common.c:218 do_syscall_64+0xdc/0x1e0 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f Local variable stack created at: __bpf_prog_run64+0x45/0xe0 kernel/bpf/core.c:2236 bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline] __bpf_prog_run include/linux/filter.h:657 [inline] bpf_prog_run include/linux/filter.h:664 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:2381 [inline] bpf_trace_run4+0x150/0x340 kernel/trace/bpf_trace.c:2422 CPU: 0 PID: 5042 Comm: syz-executor593 Not tainted 6.9.0-syzkaller-02707-g614da38e2f7a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 ===================================================== --- 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. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
