linux-kernel - [syzbot] [bluetooth?] BUG: corrupted list in hci_cmd_sync_dequeue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <67161561.050a0220.10f4f4.0042.GAE@google.com>
Date: Mon, 21 Oct 2024 01:48:33 -0700
From: syzbot <syzbot+5250d87dea2afdb718a5@...kaller.appspotmail.com>
To: johan.hedberg@...il.com, linux-bluetooth@...r.kernel.org, 
	linux-kernel@...r.kernel.org, luiz.dentz@...il.com, marcel@...tmann.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [bluetooth?] BUG: corrupted list in hci_cmd_sync_dequeue_once

Hello,

syzbot found the following issue on:

HEAD commit:    b311c1b497e5 Merge tag '6.11-rc4-server-fixes' of git://gi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10492dd3980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4fc2afd52fd008bb
dashboard link: https://syzkaller.appspot.com/bug?extid=5250d87dea2afdb718a5
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/d6f4c238ef76/disk-b311c1b4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/41d5a1c1c348/vmlinux-b311c1b4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/86f62e4350b3/bzImage-b311c1b4.xz

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

list_del corruption, ffff8880295c1780->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 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc4-syzkaller-00019-gb311c1b497e5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: hci1 hci_conn_timeout
RIP: 0010:__list_del_entry_valid_or_report+0xf4/0x140 lib/list_debug.c:56
Code: e8 d1 20 fb 06 90 0f 0b 48 c7 c7 00 9d 3f 8c 4c 89 fe e8 bf 20 fb 06 90 0f 0b 48 c7 c7 60 9d 3f 8c 4c 89 fe e8 ad 20 fb 06 90 <0f> 0b 48 c7 c7 c0 9d 3f 8c 4c 89 fe e8 9b 20 fb 06 90 0f 0b 48 c7
RSP: 0018:ffffc90000be7ad0 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000122 RCX: d39b9f85a0f3fd00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff8880295c17a0 R08: ffffffff817402dc R09: 1ffff9200017cef8
R10: dffffc0000000000 R11: fffff5200017cef9 R12: dffffc0000000000
R13: ffff8880295c1780 R14: dead000000000100 R15: ffff8880295c1780
FS:  0000000000000000(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001400 CR3: 0000000058c36000 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]
 _hci_cmd_sync_cancel_entry net/bluetooth/hci_sync.c:643 [inline]
 hci_cmd_sync_cancel_entry net/bluetooth/hci_sync.c:809 [inline]
 hci_cmd_sync_dequeue_once+0x262/0x360 net/bluetooth/hci_sync.c:828
 hci_cancel_connect_sync+0xc3/0x120
 hci_abort_conn+0x194/0x330 net/bluetooth/hci_conn.c:2951
 process_one_work kernel/workqueue.c:3231 [inline]
 process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
 worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0xf4/0x140 lib/list_debug.c:56
Code: e8 d1 20 fb 06 90 0f 0b 48 c7 c7 00 9d 3f 8c 4c 89 fe e8 bf 20 fb 06 90 0f 0b 48 c7 c7 60 9d 3f 8c 4c 89 fe e8 ad 20 fb 06 90 <0f> 0b 48 c7 c7 c0 9d 3f 8c 4c 89 fe e8 9b 20 fb 06 90 0f 0b 48 c7
RSP: 0018:ffffc90000be7ad0 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000122 RCX: d39b9f85a0f3fd00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff8880295c17a0 R08: ffffffff817402dc R09: 1ffff9200017cef8
R10: dffffc0000000000 R11: fffff5200017cef9 R12: dffffc0000000000
R13: ffff8880295c1780 R14: dead000000000100 R15: ffff8880295c1780
FS:  0000000000000000(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001400 CR3: 0000000058c36000 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 syzkaller@...glegroups.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