From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
Date: Wed, 4 Jun 2025 10:36:25 +0000 [thread overview]
Message-ID: <916e1b593d7dfc8d6286206a6ecc60bdff45a091.camel@oracle.com> (raw)
In-Reply-To: <2025060459-diaphragm-display-ba2d@gregkh>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Wed, Jun 04 2025 at 15:30:54 +0530, gregkh@linuxfoundation.org
wrote:
> On Wed, Jun 04, 2025 at 09:54:55AM +0000, Siddh Raman Pant wrote:
> > On Wed, Jun 04 2025 at 14:58:03 +0530, gregkh@linuxfoundation.org
> > wrote:
> > > Doesn't "causing corrupted memory when flashing a microcode update" fit
> > > the cve.org definition of a "vulnerabilty"?
> >
> > This only happens on CPU bring-up so I don't see it getting triggered
> > without already being exploited.
>
> If you can get the maintainers/developers involved with this change to
> agree, we will be glad to reject this.
Oops, went through it in more detail, you are right.
I should have done my homework better.
Very sorry for the noise,
Siddh
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-06-04 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025040257-CVE-2025-21991-6aae@gregkh>
2025-06-04 9:24 ` CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes Siddh Raman Pant
2025-06-04 9:28 ` gregkh
2025-06-04 9:54 ` Siddh Raman Pant
2025-06-04 10:00 ` gregkh
2025-06-04 10:36 ` Siddh Raman Pant [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=916e1b593d7dfc8d6286206a6ecc60bdff45a091.camel@oracle.com \
--to=siddh.raman.pant@oracle.com \
--cc=gregkh@linuxfoundation.org \
--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