All of lore.kernel.org
 help / color / mirror / Atom feed
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-21818: x86/xen: fix xen_hypercall_hvm() to not clobber %rbx
Date: Sun, 2 Mar 2025 15:25:50 +0100	[thread overview]
Message-ID: <2025030236-item-coral-d4b3@gregkh> (raw)
In-Reply-To: <f78c7925-8057-4503-93ec-c50386a63862@suse.com>

On Fri, Feb 28, 2025 at 08:28:48AM +0100, Juergen Gross wrote:
> On 27.02.25 21:03, Greg Kroah-Hartman wrote:
> > Description
> > ===========
> > 
> > In the Linux kernel, the following vulnerability has been resolved:
> > 
> > x86/xen: fix xen_hypercall_hvm() to not clobber %rbx
> > 
> > xen_hypercall_hvm(), which is used when running as a Xen PVH guest at
> > most only once during early boot, is clobbering %rbx. Depending on
> > whether the caller relies on %rbx to be preserved across the call or
> > not, this clobbering might result in an early crash of the system.
> > 
> > This can be avoided by using an already saved register instead of %rbx.
> > 
> > The Linux kernel CVE team has assigned CVE-2025-21818 to this issue.
> 
> Please revoke this CVE.
> 
> There is no way an unprivileged user can trigger this issue at will.
> The issue is guest local and will either happen very early at boot or
> it won't happen at all.
> 
> So no security issue.

Now rejected, thanks for the review.

greg k-h

      reply	other threads:[~2025-03-02 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 20:03 CVE-2025-21818: x86/xen: fix xen_hypercall_hvm() to not clobber %rbx Greg Kroah-Hartman
2025-02-28  7:28 ` Juergen Gross
2025-03-02 14:25   ` 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=2025030236-item-coral-d4b3@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 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.