[moderation] [bluetooth?] BUG: corrupted list in mgmt_pending_remove

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 62b5bf58b928 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17cd7f16980000
kernel config: https://syzkaller.appspot.com/x/.config?x=333ebe38d43c42e2
dashboard link: https://syzkaller.appspot.com/bug?extid=d8706ef136128955d659
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [johan....@gmail.com linux-b...@vger.kernel.org linux-...@vger.kernel.org luiz....@gmail.com mar...@holtmann.org net...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/36aadda2d784/disk-62b5bf58.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b16afb740a67/vmlinux-62b5bf58.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d4eaadcdf8c1/bzImage-62b5bf58.xz

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

list_del corruption, ffff888029187a80->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:58!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 PID: 7506 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00438-g62b5bf58b928 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:__list_del_entry_valid_or_report+0xf4/0x140 lib/list_debug.c:56
Code: e8 a1 a6 cc 06 90 0f 0b 48 c7 c7 00 f7 1f 8c 4c 89 fe e8 8f a6 cc 06 90 0f 0b 48 c7 c7 60 f7 1f 8c 4c 89 fe e8 7d a6 cc 06 90 <0f> 0b 48 c7 c7 c0 f7 1f 8c 4c 89 fe e8 6b a6 cc 06 90 0f 0b 48 c7
RSP: 0018:ffffc900130af7b8 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000122 RCX: 68025e28e05a7900
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffffff8176912c R09: fffffbfff1c39994
R10: dffffc0000000000 R11: fffffbfff1c39994 R12: dffffc0000000000
R13: ffff888023e84000 R14: dead000000000100 R15: ffff888029187a80
FS: 00007f8f2e3696c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc1abd6ff78 CR3: 000000007b332000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry_valid include/linux/list.h:124 [inline]
__list_del_entry include/linux/list.h:215 [inline]
list_del include/linux/list.h:229 [inline]
mgmt_pending_remove+0x26/0x1a0 net/bluetooth/mgmt_util.c:314
mgmt_pending_foreach+0xd1/0x130 net/bluetooth/mgmt_util.c:259
__mgmt_power_off+0x187/0x420 net/bluetooth/mgmt.c:9413
hci_dev_close_sync+0x587/0xf60 net/bluetooth/hci_sync.c:5058
hci_dev_do_close net/bluetooth/hci_core.c:556 [inline]
hci_dev_close+0x112/0x210 net/bluetooth/hci_core.c:581
sock_do_ioctl+0x158/0x460 net/socket.c:1222
sock_ioctl+0x629/0x8e0 net/socket.c:1341
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:907 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8f2d67cf69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8f2e3690c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8f2d7b3f80 RCX: 00007f8f2d67cf69
RDX: 0000000000000000 RSI: 00000000400448ca RDI: 0000000000000005
RBP: 00007f8f2d6da6fe R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f8f2d7b3f80 R15: 00007ffe5cf352c8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0xf4/0x140 lib/list_debug.c:56
Code: e8 a1 a6 cc 06 90 0f 0b 48 c7 c7 00 f7 1f 8c 4c 89 fe e8 8f a6 cc 06 90 0f 0b 48 c7 c7 60 f7 1f 8c 4c 89 fe e8 7d a6 cc 06 90 <0f> 0b 48 c7 c7 c0 f7 1f 8c 4c 89 fe e8 6b a6 cc 06 90 0f 0b 48 c7
RSP: 0018:ffffc900130af7b8 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000122 RCX: 68025e28e05a7900
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffffff8176912c R09: fffffbfff1c39994
R10: dffffc0000000000 R11: fffffbfff1c39994 R12: dffffc0000000000
R13: ffff888023e84000 R14: dead000000000100 R15: ffff888029187a80
FS: 00007f8f2e3696c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020167030 CR3: 000000007b332000 CR4: 00000000003506f0
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