BUG: corrupted list in corrupted

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 10ad6cfd Linux 4.19.148
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=102ea109900000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef9a7978d84ee42b
dashboard link: https://syzkaller.appspot.com/bug?extid=66dbd7f76c5d8712a1f9
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ab16e5900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15578e09900000

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

audit: type=1400 audit(1601192957.488:8): avc: denied { execmem } for pid=6501 comm="syz-executor576" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
hrtimer: interrupt took 46495 ns
list_del corruption, ffff8880a3a5f738->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: 6522 Comm: syz-executor576 Not tainted 4.19.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__list_del_entry_valid.cold+0x2c/0x43 lib/list_debug.c:45
Code: e2 48 c7 c7 20 f4 51 88 e8 e3 bf b8 fd 0f 0b 48 c7 c7 c0 49 18 8a e8 76 73 13 00 4c 89 ea 48 c7 c7 c0 f3 51 88 e8 c6 bf b8 fd <0f> 0b 48 c7 c7 00 4a 18 8a e8 59 73 13 00 90 90 90 90 90 90 90 90
list_del corruption, ffff88808a3d7738->next is LIST_POISON1 (dead000000000100)
RSP: 0018:ffff8880a3a5f610 EFLAGS: 00010086
------------[ cut here ]------------
RAX: 000000000000004e RBX: ffff8880a3a5f720 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815b523f RDI: ffffed101474beb4
kernel BUG at lib/list_debug.c:45!
RBP: ffff88809f500600 R08: 000000000000004e R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000002 R12: dead000000000200
R13: dead000000000100 R14: ffff8880a3a5f740 R15: 0000000000000007
FS: 00007f8d7dcc8700(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004ccc70 CR3: 0000000092ebb000 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]
__remove_wait_queue include/linux/wait.h:184 [inline]
remove_wait_queue+0x2c/0x180 kernel/sched/wait.c:44
tipc_send_group_bcast+0x34f/0xa60 net/tipc/socket.c:1022
__tipc_sendmsg+0xa2b/0x1320 net/tipc/socket.c:1311
tipc_sendmsg+0x4c/0x70 net/tipc/socket.c:1276
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc7/0x130 net/socket.c:632
___sys_sendmsg+0x3b3/0x8f0 net/socket.c:2115
__sys_sendmmsg+0x195/0x470 net/socket.c:2210
__do_sys_sendmmsg net/socket.c:2239 [inline]
__se_sys_sendmmsg net/socket.c:2236 [inline]
__x64_sys_sendmmsg+0x99/0x100 net/socket.c:2236
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x446a29
Code: e8 0c e8 ff ff 48 83 c4 18 c3 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db 06 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f8d7dcc7db8 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00000000006dbc38 RCX: 0000000000446a29
RDX: 08000000000000b0 RSI: 0000000020000a40 RDI: 0000000000000004
RBP: 00000000006dbc30 R08: 00007f8d7dcc8700 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006dbc3c
R13: 00007fff7f81f7bf R14: 00007f8d7dcc89c0 R15: 000000000000002d
Modules linked in:
---[ end trace 1417a076254b9d96 ]---
invalid opcode: 0000 [#2] PREEMPT SMP KASAN
RIP: 0010:__list_del_entry_valid.cold+0x2c/0x43 lib/list_debug.c:45
CPU: 0 PID: 6523 Comm: syz-executor576 Tainted: G D 4.19.148-syzkaller #0
Code: e2 48 c7 c7 20 f4 51 88 e8 e3 bf b8 fd 0f 0b 48 c7 c7 c0 49 18 8a e8 76 73 13 00 4c 89 ea 48 c7 c7 c0 f3 51 88 e8 c6 bf b8 fd <0f> 0b 48 c7 c7 00 4a 18 8a e8 59 73 13 00 90 90 90 90 90 90 90 90
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RSP: 0018:ffff8880a3a5f610 EFLAGS: 00010086
RIP: 0010:__list_del_entry_valid.cold+0x2c/0x43 lib/list_debug.c:45
RAX: 000000000000004e RBX: ffff8880a3a5f720 RCX: 0000000000000000
Code: e2 48 c7 c7 20 f4 51 88 e8 e3 bf b8 fd 0f 0b 48 c7 c7 c0 49 18 8a e8 76 73 13 00 4c 89 ea 48 c7 c7 c0 f3 51 88 e8 c6 bf b8 fd <0f> 0b 48 c7 c7 00 4a 18 8a e8 59 73 13 00 90 90 90 90 90 90 90 90
RDX: 0000000000000000 RSI: ffffffff815b523f RDI: ffffed101474beb4
RSP: 0018:ffff88808a3d7610 EFLAGS: 00010086
RBP: ffff88809f500600 R08: 000000000000004e R09: 0000000000000000
RAX: 000000000000004e RBX: ffff88808a3d7720 RCX: 0000000000000000
R10: 0000000000000005 R11: 0000000000000002 R12: dead000000000200
RDX: 0000000000000000 RSI: ffffffff815b523f RDI: ffffed101147aeb4
R13: dead000000000100 R14: ffff8880a3a5f740 R15: 0000000000000007
RBP: ffff8880a0c9c180 R08: 000000000000004e R09: 0000000000000000
FS: 00007f8d7dcc8700(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
R10: 0000000000000005 R11: 000000000fdf579f R12: dead000000000200
R13: dead000000000100 R14: ffff88808a3d7740 R15: 0000000000000007
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004ccc70 CR3: 0000000092ebb000 CR4: 00000000001406e0
FS: 00007f8d7dcc8700(0000) GS:ffff8880ae200000(0000) knlGS:0000000000000000
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
CR2: 00000000004ccc70 CR3: 000000008e1d8000 CR4: 00000000001406f0


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