[v6.1] WARNING in l2cap_chan_del

Hello,

syzbot found the following issue on:

HEAD commit: aa4cd140bba5 Linux 6.1.112
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=132d8f9f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=33931c04473f8585
dashboard link: https://syzkaller.appspot.com/bug?extid=7da704259ee332e4ed9d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2a9778339706/disk-aa4cd140.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b568a6da8a9b/vmlinux-aa4cd140.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c56af7eb2c4/bzImage-aa4cd140.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5264 at kernel/workqueue.c:1441 __queue_work+0xddc/0xf90
Modules linked in:
CPU: 1 PID: 5264 Comm: syz.2.277 Not tainted 6.1.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__queue_work+0xddc/0xf90 kernel/workqueue.c:1441
Code: 8b 3c 24 e8 a6 a0 88 00 e9 d9 fc ff ff e8 6c 1e 31 00 89 ee 48 c7 c7 80 99 1d 8d e8 1e 6c 0b 03 e9 1e fc ff ff e8 54 1e 31 00 <0f> 0b 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 3e 1e 31 00
RSP: 0018:ffffc9000a187518 EFLAGS: 00010087
RAX: ffffffff815990ec RBX: 00000000000b0012 RCX: 0000000000040000
RDX: ffffc9000bbb1000 RSI: 000000000000407a RDI: 000000000000407b
RBP: 0000000000010000 R08: ffffffff815a7edb R09: ffffed100b622067
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000200
R13: dffffc0000000000 R14: 0000000000000008 R15: ffff88802cfe3000
FS: 00007f5294fa16c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000201e5030 CR3: 000000007e589000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
queue_delayed_work_on+0x156/0x250 kernel/workqueue.c:1704
l2cap_chan_del+0x2cd/0x610 net/bluetooth/l2cap_core.c:695
l2cap_chan_close+0xfb/0x880 net/bluetooth/l2cap_core.c:883
l2cap_sock_shutdown+0xa5b/0xf80 net/bluetooth/l2cap_sock.c:1404
l2cap_sock_release+0x75/0x1d0 net/bluetooth/l2cap_sock.c:1448
__sock_release net/socket.c:654 [inline]
sock_close+0xcd/0x230 net/socket.c:1400
__fput+0x3f6/0x8d0 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:203
get_signal+0x15fc/0x17d0 kernel/signal.c:2647
arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f529417dff9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5294fa1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 00007f5294336130 RCX: 00007f529417dff9
RDX: 000000000000000e RSI: 0000000020000040 RDI: 0000000000000009
RBP: 00007f52941f0296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f5294336130 R15: 00007ffcbcb61dd8
</TASK>


---
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 [email protected].

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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.