linux-kernel - Re: [PATCH RFC] x86/microcode/intel: Refresh the revisions that determine old

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <F5790843-AB8B-4E07-8A62-5F777249CFCF@alien8.de>
Date: Sun, 05 Oct 2025 08:27:54 +0300
From: Borislav Petkov <bp@...en8.de>
To: Dave Hansen <dave.hansen@...el.com>,
 Xose Vazquez Perez <xose.vazquez@...il.com>
CC: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 "H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
 Josh Poimboeuf <jpoimboe@...nel.org>,
 Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
 Nikolay Borisov <nik.borisov@...e.com>,
 Alex Murray <alex.murray@...onical.com>,
 Andrew Cooper <andrew.cooper3@...rix.com>,
 Sohil Mehta <sohil.mehta@...el.com>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Dave Hansen <dave.hansen@...ux.intel.com>, X86-ML <x86@...nel.org>,
 KERNEL-ML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] x86/microcode/intel: Refresh the revisions that determine old_microcode to 20250812 (Aug 2025)

On October 5, 2025 6:58:05 AM GMT+03:00, Dave Hansen <dave.hansen@...el.com> wrote:
>On 10/4/25 19:42, Borislav Petkov wrote:
>> This is turning into exactly what I was afraid and I warned it would turn onto:
>> 
>> 1. https://git.kernel.org/tip/952df63ef426b21d6da14bb48748f12b0ae2fe36 - we *just* updated it and there's already a new one
>> 
>> 2. Random people - not Intel - are going to be sending updates too.
>> 
>> This is a mess waiting to happen. ;-/
>
>In the end, we've got an lightly documented patch that doesn't make a
>lot of sense to apply. Not exactly a unique situation. ;)
>
>Xose, do you have any specific, practical reasons this should be
>applied? Honestly, I don't hold the "HIGH" Intel SA rating in super high
>regard.

That's the problem. It'll be needless and endless discussions of the sort: oh, why do you need to update those revisions? But but, I need this and that. Oh but you don't. Blablabla... Upstream has these revisions, why aren't they backported...?

Versus: people should always update to the latest microcode and we're not tracking this in the kernel because there's really no need to.

And none of those issues exist anymore.

This is one of the reasons why I'm making sure the loader always works and is very easy to update microcode. You always update and that's it.

So you don't need any of that unnecessary work.

Thx.

Small device. Typos and formatting crap