From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/intel-microcode: security bump to version 20191112
Date: Wed, 13 Nov 2019 19:47:03 +0100 [thread overview]
Message-ID: <20191113184703.GI3419@scaer> (raw)
In-Reply-To: <20191113161849.23872-1-peter@korsgaard.com>
Peter, All,
On 2019-11-13 17:18 +0100, Peter Korsgaard spake thusly:
> Contains mitigations for the following security vulnerabilities:
>
> - CVE-2019-11135: Intel TSX Asynchronous Abort vulnerability:
> https://software.intel.com/security-software-guidance/insights/deep-dive-intel-transactional-synchronization-extensions-intel-tsx-asynchronous-abort
>
> - CVE-2019-11139: Intel Xeon Scalable Processors Voltage Setting Modulation
> vulnerability:
> https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00271.html
>
> Release notes:
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20191112
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> 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 5d340e627f..f9fce28b2d 100644
> --- a/package/intel-microcode/intel-microcode.hash
> +++ b/package/intel-microcode/intel-microcode.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> -sha256 2b6b728d351764dfbf6a9763ac96ae7e04085f382a309fed3abc0118f094c943 intel-microcode-20190918.tar.gz
> +sha256 0000f7cf96f2b07a1ba9d1fc0bcfcb49d0edb91f7d487a57a88c147e57c5873b intel-microcode-20191112.tar.gz
> sha256 1f8bf63fc2b1b486c507b98ff7d283c7eb58c7945746b94188a310d6787cbee5 license
> diff --git a/package/intel-microcode/intel-microcode.mk b/package/intel-microcode/intel-microcode.mk
> index a4d4a01f71..0492ace69e 100644
> --- a/package/intel-microcode/intel-microcode.mk
> +++ b/package/intel-microcode/intel-microcode.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -INTEL_MICROCODE_VERSION = 20190918
> +INTEL_MICROCODE_VERSION = 20191112
> 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.20.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-11-13 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 16:18 [Buildroot] [PATCH] package/intel-microcode: security bump to version 20191112 Peter Korsgaard
2019-11-13 18:47 ` Yann E. MORIN [this message]
2019-11-18 13:01 ` Peter Korsgaard
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=20191113184703.GI3419@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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