general protection fault in futex_wake (2)

6 views
Skip to first unread message

syzbot

unread,
Mar 27, 2021, 7:26:14 AM3/27/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 78fec161 Linux 4.19.183
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1535a926d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8b2beec637df5f52
dashboard link: https://syzkaller.appspot.com/bug?extid=c0d001832d61b876414c

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

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

kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 11951 Comm: syz-executor.2 Not tainted 4.19.183-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:futex_wake+0x22f/0x480 kernel/futex.c:1688
Code: 4c 39 24 24 48 8d 58 e8 0f 84 b7 01 00 00 49 bc 00 00 00 00 00 fc ff df eb 33 e8 4c 8a 0a 00 4c 8d 6b 18 4c 89 e8 48 c1 e8 03 <42> 80 3c 20 00 0f 85 c5 01 00 00 48 8b 43 18 48 89 dd 48 83 e8 18
RSP: 0018:ffff888213bafb30 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffffffffffffe8 RCX: ffffffff8157d3af
RDX: 0000000000000000 RSI: ffffffff8157d314 RDI: 0000000000000006
RBP: ffff88800010fb48 R08: 0000000000000001 R09: ffff8880afd0e500
R10: 0000000000000006 R11: 0000000000000000 R12: dffffc0000000000
R13: 0000000000000000 R14: 000000000056b000 R15: ffff8880afd0e500
FS: 0000000001f2e400(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000056bf64 CR3: 000000020774b000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_futex+0x351/0x18a0 kernel/futex.c:3895
__do_sys_futex kernel/futex.c:3951 [inline]
__se_sys_futex+0x28f/0x3b0 kernel/futex.c:3919
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x466459
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffce3b83bd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 000000000056bf6c RCX: 0000000000466459
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 000000000056bf6c
RBP: 000000000056bf60 R08: 000002ebf5b97df7 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000570060
R13: 00007ffce3b83ce0 R14: 000000000056bf60 R15: 0000000000000000
Modules linked in:
---[ end trace 22fffcb4f3405c10 ]---
RIP: 0010:futex_wake+0x22f/0x480 kernel/futex.c:1688
Code: 4c 39 24 24 48 8d 58 e8 0f 84 b7 01 00 00 49 bc 00 00 00 00 00 fc ff df eb 33 e8 4c 8a 0a 00 4c 8d 6b 18 4c 89 e8 48 c1 e8 03 <42> 80 3c 20 00 0f 85 c5 01 00 00 48 8b 43 18 48 89 dd 48 83 e8 18
RSP: 0018:ffff888213bafb30 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffffffffffffe8 RCX: ffffffff8157d3af
RDX: 0000000000000000 RSI: ffffffff8157d314 RDI: 0000000000000006
RBP: ffff88800010fb48 R08: 0000000000000001 R09: ffff8880afd0e500
R10: 0000000000000006 R11: 0000000000000000 R12: dffffc0000000000
R13: 0000000000000000 R14: 000000000056b000 R15: ffff8880afd0e500
FS: 0000000001f2e400(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000056bf64 CR3: 000000020774b000 CR4: 00000000001406f0
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

unread,
Jul 25, 2021, 7:26:19 AM7/25/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages