public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Fwd: [intel/Intel-Linux-Processor-Microcode-Data-Files] Release microcode-20260512 - microcode-20260512 Release
Date: Wed, 13 May 2026 09:51:38 +0100	[thread overview]
Message-ID: <2A1A9568-735F-4B20-B69E-678756CA06D4@ipfire.org> (raw)
In-Reply-To: <intel/Intel-Linux-Processor-Microcode-Data-Files/releases/321294731@github.com>

[-- Attachment #1: Type: text/plain, Size: 4492 bytes --]

Hello,

Is anyone up for updating this?

All the best,
-Michael

> Begin forwarded message:
> 
> From: MCU Administrator <notifications@github.com>
> Subject: [intel/Intel-Linux-Processor-Microcode-Data-Files] Release microcode-20260512 - microcode-20260512 Release
> Date: 12 May 2026 at 18:26:13 BST
> To: intel/Intel-Linux-Processor-Microcode-Data-Files <Intel-Linux-Processor-Microcode-Data-Files@noreply.github.com>
> Cc: Subscribed <subscribed@noreply.github.com>
> Reply-To: intel/Intel-Linux-Processor-Microcode-Data-Files <noreply@github.com>
> 
> 
> microcode-20260512 Release <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260512>
> Repository: intel/Intel-Linux-Processor-Microcode-Data-Files <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files> · Tag: microcode-20260512 <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/tree/microcode-20260512> · Commit: 98f8d81 <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/commit/98f8d817ca3d560c48ae988bd805d1b53b48a631> · Released by: mcu-administrator <https://github.com/mcu-administrator>
> Release Notes
> 
> microcode-20260512 <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260512>
> Purpose
> 
> Security updates for INTEL-SA-01420 <https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01420.html>
> Update for functional issues. Refer to 4th Gen Intel® Xeon® Scalable Processors Specification Update <https://cdrdv2.intel.com/v1/dl/getContent/772415> for details.
> Update for functional issues. Refer to 5th Gen Intel® Xeon® Scalable Processors Specification Update <https://cdrdv2.intel.com/v1/dl/getContent/793902> for details.
> Update for functional issues. Refer to Intel® Core™ Ultra 200 V Series Processor <https://cdrdv2.intel.com/v1/dl/getContent/827538> for details.
> Update for functional issues. Refer to Intel® Core™ Ultra Processors (Series 2) <https://cdrdv2.intel.com/v1/dl/getContent/834774> for details.
> Update for functional issues. Refer to Intel® Core™ Ultra Processors (Series 3) <https://cdrdv2.intel.com/v1/dl/getContent/869992> for details.
> Update for functional issues. Refer to Intel® Xeon® 6700 Series Processors with E-cores <https://cdrdv2.intel.com/v1/dl/getContent/820922> for details.
> Update for functional issues. Refer to Intel® Xeon® 6900/6700/6500 Series Processors with P-cores <https://cdrdv2.intel.com/v1/dl/getContent/835486> for details.
> Update for functional issues. Refer to Intel® Xeon® 6700P-B/6500P-B-Series SoC with P-Cores <https://cdrdv2.intel.com/v1/dl/getContent/843306> for details.
> New Platforms
> 
> Processor	Stepping	F-M-S/PI	Old Ver	New Ver	Products
> PTL 404	A1	06-cc-03/90		0000011b	Intel Core Ultra Processor (Series 3)
> PTL-H 484/12Xe	A0/B0	06-cc-02/90		0000011b	Intel Core Ultra Processor (Series 3)
> Updated Platforms
> 
> Processor	Stepping	F-M-S/PI	Old Ver	New Ver	Products
> ARL-H	A1	06-c5-02/82	0000011b	00000121	Core Ultra Processor (Series 2)
> ARL-S/HX (8P)	B0	06-c6-02/82	0000011b	00000121	Core Ultra Processor (Series 2)
> EMR-SP	A1	06-cf-02/87	210002d3	210002e0	Xeon Scalable Gen5
> GNR-AP/SP	Bx/Hx/Lx	06-ad-01/95	01000405	01000423	Xeon 6900/6700/6500 Series Processors with P-Cores
> GNR-D	B0/B1	06-ae-01/97	01000303	01000307	Xeon 6700P-B/6500P-B Series SoC with P-Cores
> GNR-SP R1S	Bx/Hx/Lx	06-ad-01/20	0a000133	0a000142	Xeon 6700/6500-Series Processors with P-Cores
> LNL	B0	06-bd-01/80	00000125	00000126	Core Ultra 200 V Series Processor
> SPR-SP	E4/S2	06-8f-07/87	2b000661	2b000670	Xeon Scalable Gen4
> SPR-SP	E5/S3	06-8f-08/87	2b000661	2b000670	Xeon Scalable Gen4
> SRF-AP/SP	C0	06-af-03/01	03000382	030003a3	Xeon 6900/6700-Series Processors with E-Cores
> —
> This release has 2 assets:
> 
> Source code (zip)
> Source code (tar.gz)
> Visit the release page <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260512> to download them.
> 
> —
> You are receiving this because you are watching this repository.
> View it on GitHub <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260512> or unsubscribe <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/unsubscribe_via_email/ABQGVEX7ZHHRZLHTLNIKZCT42NNDLANCNFSM4CS7UPPA> from all notifications for this repository.
> 


[-- Attachment #2: Type: text/html, Size: 9874 bytes --]

       reply	other threads:[~2026-05-13  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <intel/Intel-Linux-Processor-Microcode-Data-Files/releases/321294731@github.com>
2026-05-13  8:51 ` Michael Tremer [this message]
2026-05-13  9:06   ` Adolf Belka
2026-05-13  9:15     ` Michael Tremer

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=2A1A9568-735F-4B20-B69E-678756CA06D4@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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