From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: KAISER, fun with the CPUs -- especially Intel. Cache effects can leak non-readable memory
Date: Thu, 4 Jan 2018 01:01:52 +0100 [thread overview]
Message-ID: <20180104000152.GA29745@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hi!
I guess half of the lkml people already know, but others may have
noticed something funny/serious is going on with Intel CPUs in last
few days. And ... it is. Apparently you can read kernel memory from
userspace, abusing speculative execution on modern CPUs.
Issue was known for half a year now, and at least Intel, AMD and ARM
CPUs are affected.
https://googleprojectzero.blogspot.cz/2018/01/reading-privileged-memory-with-side.html
Grab popcorn, there is going to be a lot of fun, becuase these are CPU
bugs, not kernel bugs...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
reply other threads:[~2018-01-04 0:01 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=20180104000152.GA29745@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).