* Re: CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
[not found] <2025040257-CVE-2025-21991-6aae@gregkh>
@ 2025-06-04 9:24 ` Siddh Raman Pant
2025-06-04 9:28 ` gregkh
0 siblings, 1 reply; 5+ messages in thread
From: Siddh Raman Pant @ 2025-06-04 9:24 UTC (permalink / raw)
To: gregkh@linuxfoundation.org; +Cc: linux-kernel@vger.kernel.org
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Wed, 2 Apr 2025 13:51:58 +0100, Greg Kroah-Hartman wrote:
> In the Linux kernel, the following vulnerability has been resolved:
>
> x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
>
> [...]
>
> This does not have any security implications since flashing microcode is
> a privileged operation but I believe this has reliability implications by
> potentially corrupting memory while flashing a microcode update.
If it is explicitly specified that this does not have any security
implication, why is this a CVE?
IMO this should be rejected.
Thanks,
Siddh
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
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
0 siblings, 1 reply; 5+ messages in thread
From: gregkh @ 2025-06-04 9:28 UTC (permalink / raw)
To: Siddh Raman Pant; +Cc: linux-kernel@vger.kernel.org
On Wed, Jun 04, 2025 at 09:24:12AM +0000, Siddh Raman Pant wrote:
> On Wed, 2 Apr 2025 13:51:58 +0100, Greg Kroah-Hartman wrote:
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
> >
> > [...]
> >
> > This does not have any security implications since flashing microcode is
> > a privileged operation but I believe this has reliability implications by
> > potentially corrupting memory while flashing a microcode update.
>
> If it is explicitly specified that this does not have any security
> implication, why is this a CVE?
>
> IMO this should be rejected.
Doesn't "causing corrupted memory when flashing a microcode update" fit
the cve.org definition of a "vulnerabilty"?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
2025-06-04 9:28 ` gregkh
@ 2025-06-04 9:54 ` Siddh Raman Pant
2025-06-04 10:00 ` gregkh
0 siblings, 1 reply; 5+ messages in thread
From: Siddh Raman Pant @ 2025-06-04 9:54 UTC (permalink / raw)
To: gregkh@linuxfoundation.org; +Cc: linux-kernel@vger.kernel.org
[-- Attachment #1: Type: text/plain, Size: 322 bytes --]
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.
Thanks,
Siddh
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
2025-06-04 9:54 ` Siddh Raman Pant
@ 2025-06-04 10:00 ` gregkh
2025-06-04 10:36 ` Siddh Raman Pant
0 siblings, 1 reply; 5+ messages in thread
From: gregkh @ 2025-06-04 10:00 UTC (permalink / raw)
To: Siddh Raman Pant; +Cc: linux-kernel@vger.kernel.org
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.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
2025-06-04 10:00 ` gregkh
@ 2025-06-04 10:36 ` Siddh Raman Pant
0 siblings, 0 replies; 5+ messages in thread
From: Siddh Raman Pant @ 2025-06-04 10:36 UTC (permalink / raw)
To: gregkh@linuxfoundation.org; +Cc: linux-kernel@vger.kernel.org
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2025-06-04 10:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox