[v6.1] BUG: soft lockup in wg_packet_handshake_receive_worker

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a343b0dd87b4 Linux 6.1.30
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14cd53bd280000
kernel config: https://syzkaller.appspot.com/x/.config?x=8ec86bd749598dca
dashboard link: https://syzkaller.appspot.com/bug?extid=401ae27e931883f2256a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15f54271280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b85f25280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/aebc00d6f042/disk-a343b0dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ff0321ebb5a/vmlinux-a343b0dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c928974a56d6/Image-a343b0dd.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+401ae2...@syzkaller.appspotmail.com

watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:5:4288]
Modules linked in:
irq event stamp: 50733
hardirqs last enabled at (50732): [<ffff800008215474>] queue_work_on+0xec/0x16c kernel/workqueue.c:1549
hardirqs last disabled at (50733): [<ffff8000120f85dc>] __el1_irq arch/arm64/kernel/entry-common.c:468 [inline]
hardirqs last disabled at (50733): [<ffff8000120f85dc>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:486
softirqs last enabled at (50724): [<ffff80000ca938e0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (50728): [<ffff80000ca93828>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
CPU: 0 PID: 4288 Comm: kworker/0:5 Not tainted 6.1.30-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Workqueue: wg-kex-wg1 wg_packet_handshake_receive_worker
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : test_and_set_bit include/asm-generic/bitops/instrumented-atomic.h:72 [inline]
pc : queue_work_on+0x10c/0x16c kernel/workqueue.c:1544
lr : queue_work_on+0x108/0x16c kernel/workqueue.c:1549
sp : ffff80001ddf7660
x29: ffff80001ddf7660 x28: dfff800000000000 x27: 000000000000000b
x26: 0000000000000400 x25: ffff0000ce462b40 x24: 0000000000000000
x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000
x20: ffff0000cc4bf800 x19: 0000000000000080 x18: ffff80001ddf7000
x17: ffff8000155ad000 x16: ffff800008305074 x15: 00000000000129f0
x14: 1ffff00002ab60b0 x13: 1fffe000368b6176 x12: 0000000000000003
x11: ff80800008215490 x10: 0000000000000000 x9 : ffff800008215490
x8 : ffff0000d476d340 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000002 x1 : 0000000000000080 x0 : 0000000000000000
Call trace:
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
queue_work_on+0x10c/0x16c kernel/workqueue.c:1549
wg_queue_enqueue_per_device_and_peer drivers/net/wireguard/queueing.h:179 [inline]
wg_packet_create_data drivers/net/wireguard/send.c:320 [inline]
wg_packet_send_staged_packets+0xe8c/0x1510 drivers/net/wireguard/send.c:387
wg_packet_send_keepalive+0x140/0x240 drivers/net/wireguard/send.c:239
wg_receive_handshake_packet drivers/net/wireguard/receive.c:186 [inline]
wg_packet_handshake_receive_worker+0x594/0xc58 drivers/net/wireguard/receive.c:213
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup