From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+5feef0b9ee9c8e9e5689@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
jarkko@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] [kvm?] WARNING in kvm_arch_vcpu_ioctl_run (5)
Date: Mon, 12 Jun 2023 16:52:52 -0700 [thread overview]
Message-ID: <ZIev1Fj/PQV5lEwM@google.com> (raw)
In-Reply-To: <000000000000f316b705fdf6e2b4@google.com>
On Mon, Jun 12, 2023, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 64569520920a Merge tag 'block-6.4-2023-06-09' of git://git..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=12386cd9280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3c980bfe8b399968
> dashboard link: https://syzkaller.appspot.com/bug?extid=5feef0b9ee9c8e9e5689
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13adcb43280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13af3853280000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/4421ae3b4ee0/disk-64569520.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/9312cbb35f54/vmlinux-64569520.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/3476854febf3/bzImage-64569520.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+5feef0b9ee9c8e9e5689@syzkaller.appspotmail.com
>
> kvm_intel: 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.
> kvm: vcpu 1: requested 128 ns lapic timer period limited to 200000 ns
> kvm: vcpu 1: requested lapic timer restore with starting count register 0x390=1812281087 (231971979136 ns) > initial count (200000 ns). Using initial count to start timer.
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 5004 at arch/x86/kvm/x86.c:11099 kvm_arch_vcpu_ioctl_run+0x2379/0x2820 arch/x86/kvm/x86.c:11099
> Modules linked in:
> CPU: 1 PID: 5004 Comm: syz-executor120 Not tainted 6.4.0-rc5-syzkaller-00245-g64569520920a #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x2379/0x2820 arch/x86/kvm/x86.c:11099
KVM doesn't reject KVM_SET_SREGS with a bad CR0, which combined with an L2 that's
configured with unrestricted guest *disabled*, coerces KVM into stuffing VM86 state
to virtualize Real Mode, and eventually leads to all kinds of weirdness. Will post
a patch "shortly" (probably tomorrow at this point).
prev parent reply other threads:[~2023-06-12 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 23:14 [syzbot] [kvm?] WARNING in kvm_arch_vcpu_ioctl_run (5) syzbot
2023-06-12 23:52 ` Sean Christopherson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZIev1Fj/PQV5lEwM@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=syzbot+5feef0b9ee9c8e9e5689@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.