From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/intel-microcode: security bump to version 20201118
Date: Wed, 10 Feb 2021 20:58:23 +0100 [thread overview]
Message-ID: <87ft23k84g.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210209163641.26115-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 9 Feb 2021 17:36:40 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> 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>
Committed to 2020.02.x and 2020.11.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2021-02-10 19:58 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
2021-02-10 19:58 ` Peter Korsgaard [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=87ft23k84g.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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;
as well as URLs for NNTP newsgroup(s).