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

0 views
Skip to first unread message

syzbot

unread,
Jun 24, 2024, 11:27:20 AM (5 days ago) Jun 24
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7c16f0a4ed1c Merge tag 'i2c-for-6.10-rc5' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10837c82980000
kernel config: https://syzkaller.appspot.com/x/.config?x=12f98862a3c0c799
dashboard link: https://syzkaller.appspot.com/bug?extid=2802aae0c648c0035383
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]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/50560e9024e5/disk-7c16f0a4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/080c27daee72/vmlinux-7c16f0a4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c528e0da4544/bzImage-7c16f0a4.xz

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

list_del corruption, ffff88805d970d80->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: 11029 Comm: kworker/u9:0 Not tainted 6.10.0-rc4-syzkaller-00330-g7c16f0a4ed1c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: hci0 hci_conn_timeout
RIP: 0010:__list_del_entry_valid_or_report+0xf4/0x140 lib/list_debug.c:56
Code: e8 a1 4f cc 06 90 0f 0b 48 c7 c7 40 1b 1f 8c 4c 89 fe e8 8f 4f cc 06 90 0f 0b 48 c7 c7 a0 1b 1f 8c 4c 89 fe e8 7d 4f cc 06 90 <0f> 0b 48 c7 c7 00 1c 1f 8c 4c 89 fe e8 6b 4f cc 06 90 0f 0b 48 c7
RSP: 0018:ffffc9000cecfad0 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000122 RCX: 455f76d156aa8f00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff88805d970da0 R08: ffffffff817690bc R09: fffffbfff1c39994
R10: dffffc0000000000 R11: fffffbfff1c39994 R12: dffffc0000000000
R13: ffff88805d970d80 R14: dead000000000100 R15: ffff88805d970d80
FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e738000 CR3: 000000007cd12000 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:580 [inline]
hci_cmd_sync_cancel_entry net/bluetooth/hci_sync.c:746 [inline]
hci_cmd_sync_dequeue_once+0x262/0x360 net/bluetooth/hci_sync.c:765
hci_cancel_connect_sync+0xc3/0x120
hci_abort_conn+0x194/0x330 net/bluetooth/hci_conn.c:2943
process_one_work kernel/workqueue.c:3231 [inline]
process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
worker_thread+0x86d/0xd70 kernel/workqueue.c:3393
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 a1 4f cc 06 90 0f 0b 48 c7 c7 40 1b 1f 8c 4c 89 fe e8 8f 4f cc 06 90 0f 0b 48 c7 c7 a0 1b 1f 8c 4c 89 fe e8 7d 4f cc 06 90 <0f> 0b 48 c7 c7 00 1c 1f 8c 4c 89 fe e8 6b 4f cc 06 90 0f 0b 48 c7
RSP: 0018:ffffc9000cecfad0 EFLAGS: 00010246
RAX: 000000000000004e RBX: dead000000000122 RCX: 455f76d156aa8f00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff88805d970da0 R08: ffffffff817690bc R09: fffffbfff1c39994
R10: dffffc0000000000 R11: fffffbfff1c39994 R12: dffffc0000000000
R13: ffff88805d970d80 R14: dead000000000100 R15: ffff88805d970d80
FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555710da750 CR3: 0000000030174000 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
Reply all
Reply to author
Forward
0 new messages