[v5.15] BUG: corrupted list in mgmt_pending_remove

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1302f5da580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=2ddf7c7bd890988ef41a
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz

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

list_del corruption, ffff88802ab44e80->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:55!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4197 Comm: kworker/u5:4 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: hci0 hci_power_on
RIP: 0010:__list_del_entry_valid+0xe5/0x120 lib/list_debug.c:53
Code: 48 89 de e8 ed 9b c9 05 0f 0b 48 c7 c7 00 fd 79 8a 48 89 de e8 dc 9b c9 05 0f 0b 48 c7 c7 60 fd 79 8a 48 89 de e8 cb 9b c9 05 <0f> 0b 48 c7 c7 c0 fd 79 8a 48 89 de e8 ba 9b c9 05 0f 0b 48 c7 c7
RSP: 0018:ffffc900033afb00 EFLAGS: 00010246
RAX: 000000000000004e RBX: ffff88802ab44e80 RCX: 3a17e44d1ee90f00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900033afc30 R08: ffff8880b9133d7f R09: 1ffff110172267af
R10: dffffc0000000000 R11: ffffed10172267b0 R12: dffffc0000000000
R13: dffffc0000000000 R14: dead000000000100 R15: dead000000000122
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8496cf5eb8 CR3: 000000002b394000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:132 [inline]
list_del include/linux/list.h:146 [inline]
mgmt_pending_remove+0x24/0x1a0 net/bluetooth/mgmt_util.c:268
hci_power_on+0x2c7/0x610 net/bluetooth/hci_core.c:2268
process_one_work+0x85f/0x1010 kernel/workqueue.c:2310
worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace 95ca6ada2511f427 ]---
RIP: 0010:__list_del_entry_valid+0xe5/0x120 lib/list_debug.c:53
Code: 48 89 de e8 ed 9b c9 05 0f 0b 48 c7 c7 00 fd 79 8a 48 89 de e8 dc 9b c9 05 0f 0b 48 c7 c7 60 fd 79 8a 48 89 de e8 cb 9b c9 05 <0f> 0b 48 c7 c7 c0 fd 79 8a 48 89 de e8 ba 9b c9 05 0f 0b 48 c7 c7
RSP: 0018:ffffc900033afb00 EFLAGS: 00010246
RAX: 000000000000004e RBX: ffff88802ab44e80 RCX: 3a17e44d1ee90f00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900033afc30 R08: ffff8880b9133d7f R09: 1ffff110172267af
R10: dffffc0000000000 R11: ffffed10172267b0 R12: dffffc0000000000
R13: dffffc0000000000 R14: dead000000000100 R15: dead000000000122
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8496cf5eb8 CR3: 000000002b394000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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