Hello,
syzbot found the following issue on:
HEAD commit: c076c79e Linux 4.19.137
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=127b0034900000
kernel config:
https://syzkaller.appspot.com/x/.config?x=b8bacc01843402f4
dashboard link:
https://syzkaller.appspot.com/bug?extid=d5bb522618cf7eb1aa95
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=17a82632900000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=13fbbe0a900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+d5bb52...@syzkaller.appspotmail.com
list_del corruption, ffff8880a0de8a88->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:45!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6492 Comm: kworker/u5:1 Not tainted 4.19.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci0 hci_rx_work
RIP: 0010:__list_del_entry_valid.cold+0x23/0x55 lib/list_debug.c:45
Code: e8 56 27 f4 fd 0f 0b 48 89 ee 48 c7 c7 c0 08 cb 87 e8 45 27 f4 fd 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 00 08 cb 87 e8 31 27 f4 fd <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 60 08 cb 87 e8 1d 27 f4 fd 0f 0b
RSP: 0018:ffff888085747920 EFLAGS: 00010286
RAX: 000000000000004e RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8154cf41 RDI: ffffed1010ae8f16
RBP: ffff8880a0de8a88 R08: 000000000000004e R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: dead000000000200
R13: dead000000000100 R14: ffff8880a0de8640 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000006e06c0 CR3: 000000009f507000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del include/linux/list.h:125 [inline]
l2cap_chan_destroy net/bluetooth/l2cap_core.c:476 [inline]
kref_put include/linux/kref.h:70 [inline]
l2cap_chan_put+0x5e/0x1c0 net/bluetooth/l2cap_core.c:493
l2cap_conless_channel net/bluetooth/l2cap_core.c:6976 [inline]
l2cap_recv_frame+0xd36/0xa550 net/bluetooth/l2cap_core.c:7023
l2cap_recv_acldata+0x80e/0x910 net/bluetooth/l2cap_core.c:7588
hci_acldata_packet net/bluetooth/hci_core.c:4178 [inline]
hci_rx_work+0x455/0xa90 net/bluetooth/hci_core.c:4364
process_one_work+0x864/0x1570 kernel/workqueue.c:2155
worker_thread+0x64c/0x1130 kernel/workqueue.c:2298
kthread+0x30b/0x410 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace 0c60d0d023b6c91d ]---
RIP: 0010:__list_del_entry_valid.cold+0x23/0x55 lib/list_debug.c:45
Code: e8 56 27 f4 fd 0f 0b 48 89 ee 48 c7 c7 c0 08 cb 87 e8 45 27 f4 fd 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 00 08 cb 87 e8 31 27 f4 fd <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 60 08 cb 87 e8 1d 27 f4 fd 0f 0b
RSP: 0018:ffff888085747920 EFLAGS: 00010286
RAX: 000000000000004e RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8154cf41 RDI: ffffed1010ae8f16
RBP: ffff8880a0de8a88 R08: 000000000000004e R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: dead000000000200
R13: dead000000000100 R14: ffff8880a0de8640 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000006e06c0 CR3: 000000009f507000 CR4: 00000000001406e0
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches