[v6.1] general protection fault in device_move

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 563edd786f0a Linux 6.1.122
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15e0f50f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b70d05b26edc7515
dashboard link: https://syzkaller.appspot.com/bug?extid=e0c10fc14a30c3df1430
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/9f111015ce9f/disk-563edd78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/821c260b7642/vmlinux-563edd78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9fba8f114c58/bzImage-563edd78.xz

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

general protection fault, probably for non-canonical address 0xdffffc000000000b: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000058-0x000000000000005f]
CPU: 0 PID: 4258 Comm: syz-executor Tainted: G W 6.1.122-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:klist_put lib/klist.c:212 [inline]
RIP: 0010:klist_del lib/klist.c:230 [inline]
RIP: 0010:klist_remove+0x1e2/0x460 lib/klist.c:249
Code: 80 3c 04 00 74 08 4c 89 ff e8 9a f5 3a f7 4d 8b 2f 49 83 e5 fe 49 8d 7d 58 48 89 f8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 05 e8 73 f5 3a f7 4d 8b 75 58 4c 89 ef e8 87 90 15
RSP: 0018:ffffc90003db7880 EFLAGS: 00010202
RAX: 000000000000000b RBX: ffffffff8e83bcc8 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000058
RBP: ffffc90003db7978 R08: dffffc0000000000 R09: fffffbfff1d0778d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11004e48c0c
R13: 0000000000000000 R14: ffff88802f3bbb80 R15: ffff888027246060
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2d6fbff8 CR3: 0000000024442000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
device_move+0x1b0/0x700 drivers/base/core.c:4632
hci_conn_del_sysfs+0xa8/0x150 net/bluetooth/hci_sysfs.c:73
hci_conn_cleanup+0x5a0/0x740 net/bluetooth/hci_conn.c:172
hci_conn_del+0x417/0x6c0 net/bluetooth/hci_conn.c:1151
hci_conn_hash_flush+0x205/0x2a0 net/bluetooth/hci_conn.c:2510
hci_dev_close_sync+0x9a9/0xfc0 net/bluetooth/hci_sync.c:5177
hci_dev_do_close net/bluetooth/hci_core.c:510 [inline]
hci_unregister_dev+0x207/0x500 net/bluetooth/hci_core.c:2707
vhci_release+0x7f/0xd0 drivers/bluetooth/hci_vhci.c:573
__fput+0x3f6/0x8d0 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:203
exit_task_work include/linux/task_work.h:39 [inline]
do_exit+0xa6e/0x26a0 kernel/exit.c:871
do_group_exit+0x202/0x2b0 kernel/exit.c:1021
__do_sys_exit_group kernel/exit.c:1032 [inline]
__se_sys_exit_group kernel/exit.c:1030 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1030
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f84f8185d29
Code: Unable to access opcode bytes at 0x7f84f8185cff.
RSP: 002b:00007ffcfd5c0128 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f84f8201966 RCX: 00007f84f8185d29
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000016 R08: 00007ffcfd5bdec6 R09: 00007ffcfd5c13e0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffcfd5c13e0
R13: 00007f84f82018f4 R14: 000055558d14f4a8 R15: 0000000000000002
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:klist_put lib/klist.c:212 [inline]
RIP: 0010:klist_del lib/klist.c:230 [inline]
RIP: 0010:klist_remove+0x1e2/0x460 lib/klist.c:249
Code: 80 3c 04 00 74 08 4c 89 ff e8 9a f5 3a f7 4d 8b 2f 49 83 e5 fe 49 8d 7d 58 48 89 f8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 05 e8 73 f5 3a f7 4d 8b 75 58 4c 89 ef e8 87 90 15
RSP: 0018:ffffc90003db7880 EFLAGS: 00010202
RAX: 000000000000000b RBX: ffffffff8e83bcc8 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000058
RBP: ffffc90003db7978 R08: dffffc0000000000 R09: fffffbfff1d0778d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11004e48c0c
R13: 0000000000000000 R14: ffff88802f3bbb80 R15: ffff888027246060
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6f36b6dfa0 CR3: 0000000059734000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 80 3c 04 00 cmpb $0x0,(%rsp,%rax,1)
4: 74 08 je 0xe
6: 4c 89 ff mov %r15,%rdi
9: e8 9a f5 3a f7 call 0xf73af5a8
e: 4d 8b 2f mov (%r15),%r13
11: 49 83 e5 fe and $0xfffffffffffffffe,%r13
15: 49 8d 7d 58 lea 0x58(%r13),%rdi
19: 48 89 f8 mov %rdi,%rax
1c: 48 c1 e8 03 shr $0x3,%rax
20: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
27: fc ff df
* 2a: 80 3c 08 00 cmpb $0x0,(%rax,%rcx,1) <-- trapping instruction
2e: 74 05 je 0x35
30: e8 73 f5 3a f7 call 0xf73af5a8
35: 4d 8b 75 58 mov 0x58(%r13),%r14
39: 4c 89 ef mov %r13,%rdi
3c: e8 .byte 0xe8
3d: 87 .byte 0x87
3e: 90 nop
3f: 15 .byte 0x15


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