From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/intel-microcode: security bump version to 20260812
Date: Sun, 16 Aug 2026 09:56:10 +0200 [thread overview]
Message-ID: <45690d9185535ded8563468368b9bc40@free.fr> (raw)
In-Reply-To: <20260816073211.1830243-1-bernd@kuhls.net>
On 16/08/2026 09:32, Bernd Kuhls wrote:
> 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>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-16 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 7:32 [Buildroot] [PATCH 1/1] package/intel-microcode: security bump version to 20260812 Bernd Kuhls
2026-08-16 7:56 ` Julien Olivain via buildroot [this message]
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=45690d9185535ded8563468368b9bc40@free.fr \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
/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