From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/intel-microcode: security bump to version 20201118
Date: Tue, 9 Feb 2021 19:22:42 +0100 [thread overview]
Message-ID: <20210209182242.GB1679218@scaer> (raw)
In-Reply-To: <20210209163641.26115-1-peter@korsgaard.com>
Pter, All,
On 2021-02-09 17:36 +0100, Peter Korsgaard spake thusly:
> Fixes the following security issues:
>
> - CVE-2020-8694: Insufficient access control in the Linux kernel driver for
> some Intel(R) Processors may allow an authenticated user to potentially
> enable information disclosure via local access.
>
> https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00389.html
>
> - CVE-2020-8695: Observable discrepancy in the RAPL interface for some
> Intel(R) Processors may allow a privileged user to potentially enable
> information disclosure via local access.
>
> https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00389.html
>
> - CVE-2020-8698: Improper removal of sensitive information before storage or
> transfer in some Intel(R) Processors may allow an authenticated user to
> potentially enable information disclosure via local access.
>
> https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00381.html
>
> 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 e8005bcff6..289428b4b3 100644
> --- a/package/intel-microcode/intel-microcode.hash
> +++ b/package/intel-microcode/intel-microcode.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> -sha256 eb4f939421ac6cdea3c586c9d984ec518320f00c07eb2b3d6754309c83c93371 intel-microcode-20200616.tar.gz
> +sha256 e42a264b7b86e80d013d6d00062467352c1f37e0aaea10fe5b51e4d8687921ab intel-microcode-20201118.tar.gz
> sha256 d9e989e1a7747f3ce93cb749aceca67a430d36c9bebc6e3205e0b3af3ca6304b license
> diff --git a/package/intel-microcode/intel-microcode.mk b/package/intel-microcode/intel-microcode.mk
> index 043367770b..5a13ca2cbe 100644
> --- a/package/intel-microcode/intel-microcode.mk
> +++ b/package/intel-microcode/intel-microcode.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -INTEL_MICROCODE_VERSION = 20200616
> +INTEL_MICROCODE_VERSION = 20201118
> 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:[~2021-02-09 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 16:36 [Buildroot] [PATCH] package/intel-microcode: security bump to version 20201118 Peter Korsgaard
2021-02-09 18:22 ` Yann E. MORIN [this message]
2021-02-10 19:58 ` 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=20210209182242.GB1679218@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