From: Sean Christopherson <seanjc@google.com>
To: Red Hat Product Security <secalert@redhat.com>
Cc: mingo@redhat.com, bp@alien8.de, pgn@zju.edu.cn,
pbonzini@redhat.com, wanpengli@tencent.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
kangel@zju.edu.cn, syzkaller@googlegroups.com,
jmattson@google.com, vkuznets@redhat.com,
dave.hansen@linux.intel.com, linux-sgx@vger.kernel.org,
jarkko@kernel.org, joro@8bytes.org, hpa@zytor.com
Subject: Re: 'WARNING in vcpu_enter_guest' bug in arch/x86/kvm/x86.c:9877
Date: Fri, 17 Jun 2022 16:28:39 +0000 [thread overview]
Message-ID: <Yqyrt71TG1v0gPSf@google.com> (raw)
In-Reply-To: <25270242.531.1655475119097@app133160.ycg3.service-now.com>
On Fri, Jun 17, 2022, Red Hat Product Security wrote:
> Hello!
>
> INC2131147 ('WARNING in vcpu_enter_guest' bug in arch/x86/kvm/x86.c:9877) is pending your review.
>
> Opened for: pgn@zju.edu.cn
> Followers: Paolo Bonzini, seanjc@google.com, Vitaly Kuznetsov, wanpengli@tencent.com, jmattson@google.com, joro@8bytes.org, tglx@linutronix.de, Ingo Molnar, 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, kangel@zju.edu.cn, syzkaller@googlegroups.com
>
> Mauro Matteo Cascella updated your request with the following comments:
>
> Hi Sean,
> Thanks for the fix: https://github.com/torvalds/linux/commit/423ecfea77dda83823c71b0fad1c2ddb2af1e5fc [https://github.com/torvalds/linux/commit/423ecfea77dda83823c71b0fad1c2ddb2af1e5fc].
> Is this CVE worthy? As /dev/kvm is world accessible and unprivileged users could trigger the bug IIUC. We (Red Hat) can assign one if needed.
IMO, it's not CVE worthy. Unprivileged users can trigger the bug, but the bug
itself is not harmful to the system at large, only to that user's VM/workload.
The splat is a WARN_ON_ONCE() so it won't spam the kernel log. panic_on_warn
would be problematic, but assigning a CVE for every WARN seems excessive.
next parent reply other threads:[~2022-06-17 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25270242.531.1655475119097@app133160.ycg3.service-now.com>
2022-06-17 16:28 ` Sean Christopherson [this message]
[not found] <ca5aa7c.e8ca9.17f71bde91a.Coremail.pgn@zju.edu.cn>
2022-04-15 21:09 ` 'WARNING in vcpu_enter_guest' bug in arch/x86/kvm/x86.c:9877 Sean Christopherson
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=Yqyrt71TG1v0gPSf@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=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kangel@zju.edu.cn \
--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=pgn@zju.edu.cn \
--cc=secalert@redhat.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox