From: Michal Hocko <mhocko@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Juergen Gross <jgross@suse.com>,
Sean Christopherson <seanjc@google.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: CVE-2023-52514: x86/reboot: VMCLEAR active VMCSes before emergency reboot
Date: Mon, 11 Mar 2024 11:32:49 +0100 [thread overview]
Message-ID: <Ze7d0YCDKdu_LJWc@tiehlicka> (raw)
In-Reply-To: <2024030251-CVE-2023-52514-c93d@gregkh>
On Sat 02-03-24 22:52:59, Greg KH wrote:
> Description
> ===========
>
> In the Linux kernel, the following vulnerability has been resolved:
>
> x86/reboot: VMCLEAR active VMCSes before emergency reboot
>
> VMCLEAR active VMCSes before any emergency reboot, not just if the kernel
> may kexec into a new kernel after a crash. Per Intel's SDM, the VMX
> architecture doesn't require the CPU to flush the VMCS cache on INIT. If
> an emergency reboot doesn't RESET CPUs, cached VMCSes could theoretically
> be kept and only be written back to memory after the new kernel is booted,
> i.e. could effectively corrupt memory after reboot.
>
> Opportunistically remove the setting of the global pointer to NULL to make
> checkpatch happy.
>
> The Linux kernel CVE team has assigned CVE-2023-52514 to this issue.
I do not really see the security aspect of this fix. Guests systems
shouldn't be able to trigger host reboot nor any untrusted entity should
on the host either or this would be a serious security hole.
Or am I missing something?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2024-03-11 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 21:52 CVE-2023-52514: x86/reboot: VMCLEAR active VMCSes before emergency reboot Greg Kroah-Hartman
2024-03-11 10:32 ` Michal Hocko [this message]
2024-03-11 13:42 ` Lee Jones
2024-03-11 16:07 ` Sean Christopherson
2024-03-11 16:15 ` Lee Jones
2024-03-11 16:11 ` REJECTED: " Lee Jones
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=Ze7d0YCDKdu_LJWc@tiehlicka \
--to=mhocko@suse.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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 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.