From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: CVE-2018-3665 mitigation in Linux
Date: Wed, 20 Jun 2018 17:16:02 +0200 [thread overview]
Message-ID: <d854d9ca-2fe4-ad66-7699-6fdd05032e51@link38.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
Hello,
it occurred to me lately that I was unaware of any mitigations against
CVE-2018-3665 (Spectre v5?/Lazy FPU), which might be used to extract
even AES keys from certain CPUs if AES-NI is used.
According to https://blog.cyberus-technology.de/posts/2018-06-06-intel-lazyfp-vulnerability.html ,
countermeasures have been introduced against this back in Linux kernel 4.9,
so the upcoming IPFire release is safe.
Just thought you might want to know.
Best regards,
Peter Müller
--
"We don't care. We don't have to. We're the Phone Company."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2018-06-20 15:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d854d9ca-2fe4-ad66-7699-6fdd05032e51@link38.eu \
--to=peter.mueller@link38.eu \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox