[syzbot] [kernel?] general protection fault in device_move

[syzbot <syzbot+1f4e278e8e1a9b01f95f@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    dd7207838d38 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17f7c6c0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e6d63a300b6a84a4
dashboard link: https://syzkaller.appspot.com/bug?extid=1f4e278e8e1a9b01f95f
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/d2e97bd9853a/disk-dd720783.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/02b4c391d07a/vmlinux-dd720783.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eaa4c64e1e50/bzImage-dd720783.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc000000000b: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000058-0x000000000000005f]
CPU: 0 UID: 0 PID: 7855 Comm: syz-executor Not tainted 6.12.0-rc7-syzkaller-01770-gdd7207838d38 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:klist_put lib/klist.c:212 [inline]
RIP: 0010:klist_del lib/klist.c:230 [inline]
RIP: 0010:klist_remove+0x1e8/0x480 lib/klist.c:249
Code: 3c 06 00 74 08 4c 89 ff e8 65 a6 40 f6 4d 8b 27 49 83 e4 fe 49 8d 7c 24 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 3d a6 40 f6 4d 8b 6c 24 58 4c 89 e7 e8 10 a5
RSP: 0018:ffffc9000ad178c0 EFLAGS: 00010202
RAX: 000000000000000b RBX: ffffffff9003e3c8 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000058
RBP: ffffc9000ad179b0 R08: ffffffff9003e363 R09: 1ffffffff2007c6c
R10: dffffc0000000000 R11: fffffbfff2007c6d R12: 0000000000000000
R13: ffffffff9003e3c0 R14: 1ffff11029a9c40c R15: ffff88814d4e2060
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffa5b58fd8 CR3: 0000000031058000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 device_move+0x1b4/0x710 drivers/base/core.c:4643
 hci_conn_del_sysfs+0xac/0x160 net/bluetooth/hci_sysfs.c:75
 hci_conn_cleanup net/bluetooth/hci_conn.c:174 [inline]
 hci_conn_del+0x8c4/0xc40 net/bluetooth/hci_conn.c:1164
 hci_conn_hash_flush+0x18e/0x240 net/bluetooth/hci_conn.c:2699
 hci_dev_close_sync+0xa42/0x11c0 net/bluetooth/hci_sync.c:5212
 hci_dev_do_close net/bluetooth/hci_core.c:483 [inline]
 hci_unregister_dev+0x20b/0x510 net/bluetooth/hci_core.c:2698
 vhci_release+0x80/0xd0 drivers/bluetooth/hci_vhci.c:664
 __fput+0x23f/0x880 fs/file_table.c:431
 task_work_run+0x24f/0x310 kernel/task_work.c:239
 exit_task_work include/linux/task_work.h:43 [inline]
 do_exit+0xa2f/0x28e0 kernel/exit.c:939
 do_group_exit+0x207/0x2c0 kernel/exit.c:1088
 __do_sys_exit_group kernel/exit.c:1099 [inline]
 __se_sys_exit_group kernel/exit.c:1097 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1097
 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232
 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:0x7f3121d7e819
Code: Unable to access opcode bytes at 0x7f3121d7e7ef.
RSP: 002b:00007ffcf8975c18 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f3121d7e819
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000043
RBP: 00007f3121dde5b0 R08: 00007ffcf89739b7 R09: 0000000000000003
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000003 R14: 00000000ffffffff R15: 00007ffcf8975dc0
 </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+0x1e8/0x480 lib/klist.c:249
Code: 3c 06 00 74 08 4c 89 ff e8 65 a6 40 f6 4d 8b 27 49 83 e4 fe 49 8d 7c 24 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 3d a6 40 f6 4d 8b 6c 24 58 4c 89 e7 e8 10 a5
RSP: 0018:ffffc9000ad178c0 EFLAGS: 00010202
RAX: 000000000000000b RBX: ffffffff9003e3c8 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000058
RBP: ffffc9000ad179b0 R08: ffffffff9003e363 R09: 1ffffffff2007c6c
R10: dffffc0000000000 R11: fffffbfff2007c6d R12: 0000000000000000
R13: ffffffff9003e3c0 R14: 1ffff11029a9c40c R15: ffff88814d4e2060
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000607f8000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	3c 06                	cmp    $0x6,%al
   2:	00 74 08 4c          	add    %dh,0x4c(%rax,%rcx,1)
   6:	89 ff                	mov    %edi,%edi
   8:	e8 65 a6 40 f6       	call   0xf640a672
   d:	4d 8b 27             	mov    (%r15),%r12
  10:	49 83 e4 fe          	and    $0xfffffffffffffffe,%r12
  14:	49 8d 7c 24 58       	lea    0x58(%r12),%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 3d a6 40 f6       	call   0xf640a672
  35:	4d 8b 6c 24 58       	mov    0x58(%r12),%r13
  3a:	4c 89 e7             	mov    %r12,%rdi
  3d:	e8                   	.byte 0xe8
  3e:	10                   	.byte 0x10
  3f:	a5                   	movsl  %ds:(%rsi),%es:(%rdi)


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