WARNING in kvm_arch_vcpu_ioctl_run
15 views
Skip to first unread message
syzbot
Jun 17, 2019, 6:07:06 AM6/17/19
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 7aa823a9 Linux 4.19.51
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11559f46a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=57222bc62f28e3a6
dashboard link: https://syzkaller.appspot.com/bug?extid=1aae724aec7340740567
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1179784ea00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156fb82aa00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+1aae72...@syzkaller.appspotmail.com
audit: type=1400 audit(1560761983.600:36): avc: denied { map } for
pid=8053 comm="syz-executor334" path="/root/syz-executor334092717"
dev="sda1" ino=16484 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for
details.
WARNING: CPU: 1 PID: 8055 at arch/x86/kvm/x86.c:7993
kvm_arch_vcpu_ioctl_run+0x1cc/0x16c0 arch/x86/kvm/x86.c:7993
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8055 Comm: syz-executor334 Not tainted 4.19.51 #23
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
panic+0x263/0x507 kernel/panic.c:185
__warn.cold+0x20/0x4a kernel/panic.c:540
report_bug+0x263/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x204/0x360 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1013
RIP: 0010:kvm_arch_vcpu_ioctl_run+0x1cc/0x16c0 arch/x86/kvm/x86.c:7993
Code: 80 3c 02 00 0f 85 cf 13 00 00 49 8b 9c 24 20 2c 00 00 31 ff 48 89 de
e8 72 37 5d 00 48 85 db 0f 84 1e 0c 00 00 e8 c4 35 5d 00 <0f> 0b e8 bd 35
5d 00 49 8d 7e 01 48 b8 00 00 00 00 00 fc ff df 48
RSP: 0018:ffff88809843fb38 EFLAGS: 00010293
RAX: ffff88809922c0c0 RBX: 0000000000000001 RCX: ffffffff810ddd84
RDX: 0000000000000000 RSI: ffffffff810dd12c RDI: 0000000000000005
RBP: ffff88809843fb98 R08: ffff88809922c0c0 R09: ffffed1015d24733
R10: ffffed1015d24732 R11: ffff8880ae923993 R12: ffff888073ca8040
R13: 0000000000000000 R14: ffff8880a5455000 R15: ffff888099878a00
kvm_vcpu_ioctl+0x4dc/0xf90 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2594
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xd5f/0x1380 fs/ioctl.c:688
ksys_ioctl+0xab/0xd0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:710
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x448cb9
Code: e8 8c b0 02 00 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 4b 0a fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f54f9f0ece8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006ddc58 RCX: 0000000000448cb9
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00000000006ddc50 R08: 00007f54f9f0f700 R09: 0000000000000000
R10: 00007f54f9f0f700 R11: 0000000000000246 R12: 00000000006ddc5c
R13: 00007ffe5c17204f R14: 00007f54f9f0f9c0 R15: 20c49ba5e353f7cf
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot found the following crash on:
HEAD commit: 7aa823a9 Linux 4.19.51
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11559f46a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=57222bc62f28e3a6
dashboard link: https://syzkaller.appspot.com/bug?extid=1aae724aec7340740567
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1179784ea00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156fb82aa00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+1aae72...@syzkaller.appspotmail.com
audit: type=1400 audit(1560761983.600:36): avc: denied { map } for
pid=8053 comm="syz-executor334" path="/root/syz-executor334092717"
dev="sda1" ino=16484 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for
details.
WARNING: CPU: 1 PID: 8055 at arch/x86/kvm/x86.c:7993
kvm_arch_vcpu_ioctl_run+0x1cc/0x16c0 arch/x86/kvm/x86.c:7993
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8055 Comm: syz-executor334 Not tainted 4.19.51 #23
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
panic+0x263/0x507 kernel/panic.c:185
__warn.cold+0x20/0x4a kernel/panic.c:540
report_bug+0x263/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x204/0x360 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1013
RIP: 0010:kvm_arch_vcpu_ioctl_run+0x1cc/0x16c0 arch/x86/kvm/x86.c:7993
Code: 80 3c 02 00 0f 85 cf 13 00 00 49 8b 9c 24 20 2c 00 00 31 ff 48 89 de
e8 72 37 5d 00 48 85 db 0f 84 1e 0c 00 00 e8 c4 35 5d 00 <0f> 0b e8 bd 35
5d 00 49 8d 7e 01 48 b8 00 00 00 00 00 fc ff df 48
RSP: 0018:ffff88809843fb38 EFLAGS: 00010293
RAX: ffff88809922c0c0 RBX: 0000000000000001 RCX: ffffffff810ddd84
RDX: 0000000000000000 RSI: ffffffff810dd12c RDI: 0000000000000005
RBP: ffff88809843fb98 R08: ffff88809922c0c0 R09: ffffed1015d24733
R10: ffffed1015d24732 R11: ffff8880ae923993 R12: ffff888073ca8040
R13: 0000000000000000 R14: ffff8880a5455000 R15: ffff888099878a00
kvm_vcpu_ioctl+0x4dc/0xf90 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2594
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xd5f/0x1380 fs/ioctl.c:688
ksys_ioctl+0xab/0xd0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:710
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x448cb9
Code: e8 8c b0 02 00 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 4b 0a fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f54f9f0ece8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006ddc58 RCX: 0000000000448cb9
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00000000006ddc50 R08: 00007f54f9f0f700 R09: 0000000000000000
R10: 00007f54f9f0f700 R11: 0000000000000246 R12: 00000000006ddc5c
R13: 00007ffe5c17204f R14: 00007f54f9f0f9c0 R15: 20c49ba5e353f7cf
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot
Jun 25, 2019, 7:07:06 PM6/25/19
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: bc2bccef Linux 4.14.130
syzbot found the following crash on:
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12017871a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d6a6b0abab548b75
dashboard link: https://syzkaller.appspot.com/bug?extid=d8f921b63518234f6a20
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1470c541a00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12076451a00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
audit: type=1400 audit(1561500143.353:36): avc: denied { map } for
pid=7070 comm="syz-executor399" path="/root/syz-executor399564363"
dev="sda1" ino=16483 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for
details.
------------[ cut here ]------------
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for
details.
WARNING: CPU: 1 PID: 7072 at arch/x86/kvm/x86.c:7464
kvm_arch_vcpu_ioctl_run+0xf5/0x1000 arch/x86/kvm/x86.c:7464
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 7072 Comm: syz-executor399 Not tainted 4.14.130 #24
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
Google 01/01/2011
Call Trace:
dump_stack+0x138/0x19c lib/dump_stack.c:53
panic+0x1f2/0x426 kernel/panic.c:182
__warn.cold+0x2f/0x36 kernel/panic.c:546
report_bug+0x216/0x254 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x1bb/0x310 arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:314
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:960
RIP: 0010:kvm_arch_vcpu_ioctl_run+0xf5/0x1000 arch/x86/kvm/x86.c:7464
RSP: 0018:ffff888081ae7bd8 EFLAGS: 00010297
RAX: ffff888095c38140 RBX: ffff888081149000 RCX: ffff8880820f845c
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8880820f8268
RBP: ffff888081ae7c30 R08: 0000000000000001 R09: ffff888095c389e0
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880820f8040
R13: 0000000000000000 R14: ffff8880820f8040 R15: ffff8880820f8118
kvm_vcpu_ioctl+0x401/0xd10 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2588
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x7ae/0x1060 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x448cb9
RSP: 002b:00007fa5f3bcace8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006ddc58 RCX: 0000000000448cb9
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00000000006ddc50 R08: 00007fa5f3bcb700 R09: 0000000000000000
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
R10: 00007fa5f3bcb700 R11: 0000000000000246 R12: 00000000006ddc5c
R13: 00007ffc6cba3fff R14: 00007fa5f3bcb9c0 R15: 20c49ba5e353f7cf
Reply all
Reply to author
Forward
0 new messages