============================================
WARNING: possible recursive locking detected
6.12.0-rc2-next-20241011-syzkaller #0 Not tainted
--------------------------------------------
syz.4.104/5764 is trying to acquire lock:
ffffffff8f69c328 (chaoskey_list_lock){+.+.}-{3:3}, at: chaoskey_release+0x169/0x2f0 drivers/usb/misc/chaoskey.c:322

but task is already holding lock:
ffffffff8f69c328 (chaoskey_list_lock){+.+.}-{3:3}, at: chaoskey_release+0x79/0x2f0 drivers/usb/misc/chaoskey.c:299

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(chaoskey_list_lock);
  lock(chaoskey_list_lock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

1 lock held by syz.4.104/5764:
 #0: ffffffff8f69c328
 (chaoskey_list_lock
){+.+.}-{3:3}, at: chaoskey_release+0x79/0x2f0 drivers/usb/misc/chaoskey.c:299

stack backtrace:
CPU: 1 UID: 0 PID: 5764 Comm: syz.4.104 Not tainted 6.12.0-rc2-next-20241011-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_deadlock_bug+0x483/0x620 kernel/locking/lockdep.c:3037
 check_deadlock kernel/locking/lockdep.c:3089 [inline]
 validate_chain+0x15e2/0x5920 kernel/locking/lockdep.c:3891
 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
 chaoskey_release+0x169/0x2f0 drivers/usb/misc/chaoskey.c:322
 __fput+0x23c/0xa50 fs/file_table.c:434
 task_work_run+0x24f/0x310 kernel/task_work.c:228
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0xa2f/0x28e0 kernel/exit.c:938
 do_group_exit+0x207/0x2c0 kernel/exit.c:1087
 get_signal+0x16a3/0x1740 kernel/signal.c:2917
 arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0xc9/0x370 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0ab7ba6230
Code: Unable to access opcode bytes at 0x7f0ab7ba6206.
RSP: 002b:00007f0ab88c8b38 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 00007f0ab7d35f88 RCX: 00007f0ab7b7dff9
RDX: 00007f0ab88c8b40 RSI: 00007f0ab88c8c70 RDI: 0000000000000021
RBP: 00007f0ab7d35f80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f0ab7d35f8c
R13: 0000000000000000 R14: 00007ffd191c04a0 R15: 00007ffd191c0588
 </TASK>