From: Greg KH <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2025-38026: x86/sev: Do not touch VMSA pages during SNP guest memory kdump
Date: Wed, 18 Jun 2025 13:21:21 +0200 [thread overview]
Message-ID: <2025061809-cattishly-refutable-956e@gregkh> (raw)
In-Reply-To: <43a8d610-68b9-4107-9df6-827535022543@suse.com>
On Wed, Jun 18, 2025 at 11:57:22AM +0200, Juergen Gross wrote:
> On 18.06.25 11:29, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman <gregkh@kernel.org>
> >
> > Description
> > ===========
> >
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > x86/sev: Do not touch VMSA pages during SNP guest memory kdump
> >
> > When kdump is running makedumpfile to generate vmcore and dump SNP guest
> > memory it touches the VMSA page of the vCPU executing kdump.
> >
> > It then results in unrecoverable #NPF/RMP faults as the VMSA page is
> > marked busy/in-use when the vCPU is running and subsequently a causes
> > guest softlockup/hang.
> >
> > Additionally, other APs may be halted in guest mode and their VMSA pages
> > are marked busy and touching these VMSA pages during guest memory dump
> > will also cause #NPF.
> >
> > Issue AP_DESTROY GHCB calls on other APs to ensure they are kicked out
> > of guest mode and then clear the VMSA bit on their VMSA pages.
> >
> > If the vCPU running kdump is an AP, mark it's VMSA page as offline to
> > ensure that makedumpfile excludes that page while dumping guest memory.
> >
> > The Linux kernel CVE team has assigned CVE-2025-38026 to this issue.
>
> I don't see how this issue could be triggered by an unprivileged user.
> I think this CVE should be revoked.
Now rejected, thanks for the review.
greg k-h
prev parent reply other threads:[~2025-06-18 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025061848-CVE-2025-38026-5674@gregkh>
2025-06-18 9:57 ` CVE-2025-38026: x86/sev: Do not touch VMSA pages during SNP guest memory kdump Juergen Gross
2025-06-18 11:21 ` Greg KH [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=2025061809-cattishly-refutable-956e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox