Hello, syzbot found the following issue on: HEAD commit: d7e78951a8b8 Merge tag 'net-6.11-rc0' of git://git.kernel... git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=105a2f31980000 kernel config: https://syzkaller.appspot.com/x/.config?x=8d1cf7c29e32ce12 dashboard link: https://syzkaller.appspot.com/bug?extid=b170dbf55520ebf5969a 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/3c208b51873e/disk-d7e78951.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/adec146cf41c/vmlinux-d7e78951.xz kernel image: https://storage.googleapis.com/syzbot-assets/52f09b8f7356/bzImage-d7e78951.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+b170dbf55520ebf5969a@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ ODEBUG: free active (active state 0) object: ffff888042b68978 object type: timer_list hint: hci_cmd_timeout+0x0/0x1e0 WARNING: CPU: 0 PID: 12907 at lib/debugobjects.c:518 debug_print_object+0x17a/0x1f0 lib/debugobjects.c:515 Modules linked in: CPU: 0 PID: 12907 Comm: syz-executor Not tainted 6.10.0-syzkaller-09703-gd7e78951a8b8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 RIP: 0010:debug_print_object+0x17a/0x1f0 lib/debugobjects.c:515 Code: e8 1b 7f 42 fd 4c 8b 0b 48 c7 c7 c0 72 20 8c 48 8b 74 24 08 48 89 ea 44 89 e1 4d 89 f8 ff 34 24 e8 db 5b 9e fc 48 83 c4 08 90 <0f> 0b 90 90 ff 05 fc 35 f8 0a 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 RSP: 0018:ffffc9000e6bf838 EFLAGS: 00010282 RAX: da48afca993a8400 RBX: ffffffff8bccb720 RCX: ffff888030a8da00 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000 RBP: ffffffff8c207440 R08: ffffffff815565a2 R09: fffffbfff1c39f60 R10: dffffc0000000000 R11: fffffbfff1c39f60 R12: 0000000000000000 R13: ffffffff8c207358 R14: dffffc0000000000 R15: ffff888042b68978 FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f0d8f907a6c CR3: 000000000e134000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __debug_check_no_obj_freed lib/debugobjects.c:990 [inline] debug_check_no_obj_freed+0x45b/0x580 lib/debugobjects.c:1020 slab_free_hook mm/slub.c:2202 [inline] slab_free mm/slub.c:4464 [inline] kfree+0x10f/0x360 mm/slub.c:4585 hci_release_dev+0x1525/0x16b0 net/bluetooth/hci_core.c:2760 bt_host_release+0x83/0x90 net/bluetooth/hci_sysfs.c:94 device_release+0x99/0x1c0 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x22f/0x480 lib/kobject.c:737 vhci_release+0x8b/0xd0 drivers/bluetooth/hci_vhci.c:667 __fput+0x24a/0x8a0 fs/file_table.c:422 task_work_run+0x24f/0x310 kernel/task_work.c:222 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0xa2f/0x27f0 kernel/exit.c:877 do_group_exit+0x207/0x2c0 kernel/exit.c:1026 __do_sys_exit_group kernel/exit.c:1037 [inline] __se_sys_exit_group kernel/exit.c:1035 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1035 x64_sys_call+0x26c3/0x26d0 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:0x7fbfd8775b59 Code: Unable to access opcode bytes at 0x7fbfd8775b2f. RSP: 002b:00007ffda750f638 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007fbfd87e4a82 RCX: 00007fbfd8775b59 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000043 RBP: 00007fbfd87e4a94 R08: 00007ffda750d3d7 R09: 0000000000000bb8 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000006 R13: 0000000000000bb8 R14: 000000000003e8dd R15: 000000000003e8ae </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 syzkaller@xxxxxxxxxxxxxxxx. 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
