* Re: CVE-2025-38026: x86/sev: Do not touch VMSA pages during SNP guest memory kdump [not found] <2025061848-CVE-2025-38026-5674@gregkh> @ 2025-06-18 9:57 ` Juergen Gross 2025-06-18 11:21 ` Greg KH 0 siblings, 1 reply; 2+ messages in thread From: Juergen Gross @ 2025-06-18 9:57 UTC (permalink / raw) To: cve, linux-kernel [-- Attachment #1.1.1: Type: text/plain, Size: 1267 bytes --] 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. Juergen [-- Attachment #1.1.2: OpenPGP public key --] [-- Type: application/pgp-keys, Size: 3743 bytes --] [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 bytes --] ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: CVE-2025-38026: x86/sev: Do not touch VMSA pages during SNP guest memory kdump 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 0 siblings, 0 replies; 2+ messages in thread From: Greg KH @ 2025-06-18 11:21 UTC (permalink / raw) To: Juergen Gross; +Cc: cve, linux-kernel 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-06-18 11:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox