linux-kernel - Re: [PATCH v2] scripts/x86/intel: Add a script to update the minimum ucode revisions

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] [day] [month] [year] [list]

Message-ID: <791d0ed9-27ab-48bb-bacc-8332aba7398b@intel.com>
Date: Fri, 22 Aug 2025 14:52:33 -0700
From: Sohil Mehta <sohil.mehta@...el.com>
To: Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...el.com>
CC: Dave Hansen <dave.hansen@...ux.intel.com>, <x86@...nel.org>, "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>, Andrew Cooper
	<andrew.cooper3@...rix.com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] scripts/x86/intel: Add a script to update the minimum
 ucode revisions

On 8/22/2025 12:27 PM, Borislav Petkov wrote:
> On Fri, Aug 22, 2025 at 12:16:59PM -0700, Dave Hansen wrote:
>> Ahh, gotcha. Should we slap something like this in the script?
>>
>> 	This script is intended to be run in response to releases of the
>> 	official Intel microcode github repository[link]. Typically,
>> 	someone at Intel would see a new release, run this script,
>> 	refresh the intel-ucode-defs.h file and send a patch upstream to
>> 	update the mainline and stable versions.
> 
> Yap, thanks!
> 

Thanks! Here is the updated help description in the script:

DESCRIPTION = f"""
For Intel CPUs, update the microcode revisions that determine
X86_BUG_OLD_MICROCODE.

This script is intended to be run in response to releases of the
official Intel microcode GitHub repository:
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git

It takes the Intel microcode files as input and uses iucode-tool to
extract the revision information. It prints the output in the format
expected by intel-ucode-defs.h.

Usage:
    ./{script} /path/to/microcode/files > /path/to/intel-ucode-defs.h

Typically, someone at Intel would see a new release, run this script,
refresh the intel-ucode-defs.h file, and send a patch upstream to update
the mainline and stable versions.
"""

If there are no other comments, I'll send out a revised version with an
updated commit message early next week.