[v5.15] WARNING in l2cap_chan_del (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f301b9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=875d98826c53bf16
dashboard link: https://syzkaller.appspot.com/bug?extid=e80f8d17e58c53fcbf7a
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/f227a150ea92/disk-4878aadf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6cfc50bf8b4e/vmlinux-4878aadf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23f7adc3c761/bzImage-4878aadf.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 8287 at kernel/workqueue.c:1453 __queue_work+0xbaf/0xd00
Modules linked in:
CPU: 1 PID: 8287 Comm: syz.2.1276 Not tainted 5.15.161-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:__queue_work+0xbaf/0xd00 kernel/workqueue.c:1453
Code: 7c 24 10 e8 63 68 77 00 e9 1c fd ff ff e8 09 9a 2d 00 89 ee 48 c7 c7 20 17 7d 8c e8 8b cf d7 02 e9 64 fc ff ff e8 f1 99 2d 00 <0f> 0b 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 db 99 2d 00
RSP: 0018:ffffc90003047bf8 EFLAGS: 00010087
RAX: ffffffff8152c0df RBX: 00000000000b0012 RCX: 0000000000040000
RDX: ffffc9000b70c000 RSI: 000000000000bc02 RDI: 000000000000bc03
RBP: 0000000000010000 R08: ffffffff8153a37b R09: ffffed100f5b5828
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8880189d7000 R14: 0000000000000008 R15: 0000000000000000
FS: 00007fa2c0c9a6c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe10c73b000 CR3: 000000007d900000 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:1715
l2cap_chan_del+0x2cd/0x610 net/bluetooth/l2cap_core.c:671
l2cap_chan_close+0x100/0x880 net/bluetooth/l2cap_core.c:859
l2cap_sock_shutdown+0x3b8/0x870 net/bluetooth/l2cap_sock.c:1378
__sys_shutdown_sock net/socket.c:2270 [inline]
__sys_shutdown net/socket.c:2282 [inline]
__do_sys_shutdown net/socket.c:2290 [inline]
__se_sys_shutdown+0x147/0x1a0 net/socket.c:2288
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fa2c225bbd9
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:00007fa2c0c9a048 EFLAGS: 00000246 ORIG_RAX: 0000000000000030
RAX: ffffffffffffffda RBX: 00007fa2c23ea110 RCX: 00007fa2c225bbd9
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000004
RBP: 00007fa2c22caa98 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fa2c23ea110 R15: 00007ffefaa08d88
</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 syzk...@googlegroups.com.

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