Hello, syzbot found the following issue on: HEAD commit: 2ccbdf43d5e7 Merge tag 'for-linus' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=16f23146980000 kernel config: https://syzkaller.appspot.com/x/.config?x=81c0d76ceef02b39 dashboard link: https://syzkaller.appspot.com/bug?extid=0dc211bc2adb944e1fd6 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2ccbdf43.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/13cdb5bfbafa/vmlinux-2ccbdf43.xz kernel image: https://storage.googleapis.com/syzbot-assets/7a14f5d07f81/bzImage-2ccbdf43.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0dc211bc2adb944e1fd6@xxxxxxxxxxxxxxxxxxxxxxxxx Oops: general protection fault, probably for non-canonical address 0xe003fbfffff80000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0x001fffffffc00000-0x001fffffffc00007] CPU: 1 PID: 5570 Comm: kworker/1:5 Not tainted 6.10.0-rc3-syzkaller-00044-g2ccbdf43d5e7 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Workqueue: wg-crypt-wg2 wg_packet_tx_worker RIP: 0010:get_work_pool+0xcb/0x1c0 kernel/workqueue.c:887 Code: 0d 36 00 48 89 d8 5b 5d c3 cc cc cc cc e8 8d 0d 36 00 48 81 e3 00 fe ff ff 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 da 00 00 00 48 8b 1b e8 63 0d 36 00 48 89 d8 5b RSP: 0018:ffffc90000598738 EFLAGS: 00010006 RAX: dffffc0000000000 RBX: 001fffffffc00000 RCX: ffffffff815881f2 RDX: 0003fffffff80000 RSI: ffffffff81588243 RDI: 0000000000000007 RBP: 0000000000000004 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000004 R11: 0000000000000005 R12: ffffe8ffad288cc0 R13: ffff888000596400 R14: dffffc0000000000 R15: ffff88805b626800 FS: 0000000000000000(0000) GS:ffff88802c100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000f7f75598 CR3: 0000000056bd0000 CR4: 0000000000350ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> __queue_work+0x200/0x1020 kernel/workqueue.c:2301 queue_work_on+0x11a/0x140 kernel/workqueue.c:2410 wg_queue_enqueue_per_device_and_peer drivers/net/wireguard/queueing.h:176 [inline] wg_packet_consume_data drivers/net/wireguard/receive.c:526 [inline] wg_packet_receive+0xf65/0x2350 drivers/net/wireguard/receive.c:576 wg_receive+0x74/0xc0 drivers/net/wireguard/socket.c:326 udp_queue_rcv_one_skb+0xad1/0x18b0 net/ipv4/udp.c:2131 udp_queue_rcv_skb+0x198/0xd10 net/ipv4/udp.c:2209 udp_unicast_rcv_skb+0x165/0x3b0 net/ipv4/udp.c:2369 __udp4_lib_rcv+0x2636/0x3550 net/ipv4/udp.c:2445 ip_protocol_deliver_rcu+0x30c/0x4e0 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x316/0x570 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:314 [inline] NF_HOOK include/linux/netfilter.h:308 [inline] ip_local_deliver+0x18e/0x1f0 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:460 [inline] ip_rcv_finish net/ipv4/ip_input.c:449 [inline] NF_HOOK include/linux/netfilter.h:314 [inline] NF_HOOK include/linux/netfilter.h:308 [inline] ip_rcv+0x2c5/0x5d0 net/ipv4/ip_input.c:569 __netif_receive_skb_one_core+0x199/0x1e0 net/core/dev.c:5625 __netif_receive_skb+0x1d/0x160 net/core/dev.c:5739 process_backlog+0x133/0x760 net/core/dev.c:6068 __napi_poll.constprop.0+0xb7/0x550 net/core/dev.c:6722 napi_poll net/core/dev.c:6791 [inline] net_rx_action+0x9b6/0xf10 net/core/dev.c:6907 handle_softirqs+0x216/0x8f0 kernel/softirq.c:554 do_softirq kernel/softirq.c:455 [inline] do_softirq+0xb2/0xf0 kernel/softirq.c:442 </IRQ> <TASK> __local_bh_enable_ip+0x100/0x120 kernel/softirq.c:382 wg_socket_send_skb_to_peer+0x14c/0x220 drivers/net/wireguard/socket.c:184 wg_packet_create_data_done drivers/net/wireguard/send.c:251 [inline] wg_packet_tx_worker+0x1aa/0x810 drivers/net/wireguard/send.c:276 process_one_work+0x958/0x1ad0 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:get_work_pool+0xcb/0x1c0 kernel/workqueue.c:887 Code: 0d 36 00 48 89 d8 5b 5d c3 cc cc cc cc e8 8d 0d 36 00 48 81 e3 00 fe ff ff 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 da 00 00 00 48 8b 1b e8 63 0d 36 00 48 89 d8 5b RSP: 0018:ffffc90000598738 EFLAGS: 00010006 RAX: dffffc0000000000 RBX: 001fffffffc00000 RCX: ffffffff815881f2 RDX: 0003fffffff80000 RSI: ffffffff81588243 RDI: 0000000000000007 RBP: 0000000000000004 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000004 R11: 0000000000000005 R12: ffffe8ffad288cc0 R13: ffff888000596400 R14: dffffc0000000000 R15: ffff88805b626800 FS: 0000000000000000(0000) GS:ffff88802c100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000f7f75598 CR3: 0000000056bd0000 CR4: 0000000000350ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 ---------------- Code disassembly (best guess): 0: 0d 36 00 48 89 or $0x89480036,%eax 5: d8 5b 5d fcomps 0x5d(%rbx) 8: c3 ret 9: cc int3 a: cc int3 b: cc int3 c: cc int3 d: e8 8d 0d 36 00 call 0x360d9f 12: 48 81 e3 00 fe ff ff and $0xfffffffffffffe00,%rbx 19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax 20: fc ff df 23: 48 89 da mov %rbx,%rdx 26: 48 c1 ea 03 shr $0x3,%rdx * 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction 2e: 0f 85 da 00 00 00 jne 0x10e 34: 48 8b 1b mov (%rbx),%rbx 37: e8 63 0d 36 00 call 0x360d9f 3c: 48 89 d8 mov %rbx,%rax 3f: 5b pop %rbx --- 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 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