All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] package/intel-microcode: security bump version to 20260812
Date: Sun, 16 Aug 2026 09:32:11 +0200	[thread overview]
Message-ID: <20260816073211.1830243-1-bernd@kuhls.net> (raw)

https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260812
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811

Fixes the following CVEs:

CVE-2025-31936
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01379.html

CVE-2025-31938
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01404.html

CVE-2026-20917
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01423.html

CVE-2025-35973
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01428.html

CVE-2026-20716
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01435.html

CVE-2026-20760
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01441.html

CVE-2026-20713
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01442.html

CVE-2026-20707
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01443.html

Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
Gitlab pipeline passed:
https://gitlab.com/bkuhls/buildroot/-/commits/d465150875451085466b514a4a4507586cdb965b

 package/intel-microcode/intel-microcode.hash | 2 +-
 package/intel-microcode/intel-microcode.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/intel-microcode/intel-microcode.hash b/package/intel-microcode/intel-microcode.hash
index bb36a52fc5..6f465fd679 100644
--- a/package/intel-microcode/intel-microcode.hash
+++ b/package/intel-microcode/intel-microcode.hash
@@ -1,3 +1,3 @@
 # Locally computed
-sha256  5a07ce745d0bd8b360a4713564d46d5e38be797316a52abedaff0761e1b02370  intel-microcode-20260512.tar.gz
+sha256  7614616d7b2988c278060486f47de716ef44c19317928cb45ac9e288fafd5bd1  intel-microcode-20260812.tar.gz
 sha256  03efb1491c7e899feb2665fa299363e64035e5444c1b8bc1f6ebed30de964e12  license
diff --git a/package/intel-microcode/intel-microcode.mk b/package/intel-microcode/intel-microcode.mk
index f6fbee54b4..9c97b0aa5e 100644
--- a/package/intel-microcode/intel-microcode.mk
+++ b/package/intel-microcode/intel-microcode.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-INTEL_MICROCODE_VERSION = 20260512
+INTEL_MICROCODE_VERSION = 20260812
 INTEL_MICROCODE_SITE = $(call github,intel,Intel-Linux-Processor-Microcode-Data-Files,microcode-$(INTEL_MICROCODE_VERSION))
 INTEL_MICROCODE_LICENSE = PROPRIETARY
 INTEL_MICROCODE_LICENSE_FILES = license
-- 
2.47.3

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2026-08-16  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16  7:32 Bernd Kuhls [this message]
2026-08-16  7:56 ` [Buildroot] [PATCH 1/1] package/intel-microcode: security bump version to 20260812 Julien Olivain via buildroot
2026-08-22 12:37 ` Titouan Christophe via buildroot

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=20260816073211.1830243-1-bernd@kuhls.net \
    --to=bernd@kuhls.net \
    --cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.