public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Spectre and Meltdown summary
Date: Thu, 4 Jan 2018 22:50:01 +1100	[thread overview]
Message-ID: <CAC=wYCHm1ufiDLpFi57u6pZXA06Q5X-nAG88sDyuzuhpzbgf+g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

No guarantees on accuracy...

Meltdown CVE-2017-5754 (Variant3) - userspace reads kernel memory. Intel
vulnerable, AMD not vulnerable. Issue is mitigated with KPTI (in kernel
4.14.11, Security Options -> Remove the kernel mapping in user mode
(CONFIG_PAGE_TABLE_ISOLATION), on by default for all archs in this version,
disabled by default for AMD CPUs in git 4.15). KPTI incurs a performance
hit.

Spectre CVE-2017-5753 (Variant1) and CVE-2017-5715 (Variant2) -
applications read other applications memory. Intel, AMD, ARM all
vulnerable.
Re Variant1, AMD says "Resolved by software / OS updates to be made
available by system vendors and manufacturers. Negligible performance
impact expected."
Re Variant2, AMD says "Differences in AMD architecture mean there is a near
zero risk of exploitation of this variant. Vulnerability to Variant 2 has
not been demonstrated on AMD processors to date."

Ref:
http://www.amd.com/en/corporate/speculative-execution
https://meltdownattack.com/
http://www.tomshardware.com/forum/id-3609004/cpu-security-vulnerabilities-information.html

[-- Attachment #2: Type: text/html, Size: 1380 bytes --]

             reply	other threads:[~2018-01-04 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 11:50 Adam Carter [this message]
2018-01-04 12:21 ` [gentoo-user] Re: Spectre and Meltdown summary Adam Carter
2018-01-04 21:14   ` Andrey F.
2018-01-06  0:30     ` Adam Carter
  -- strict thread matches above, loose matches on Subject: below --
2018-01-07 18:08 [gentoo-user] linux-gazette masked: The total pollution of the output :) tuxic
2018-01-07 18:31 ` Neil Bothwick
2018-01-07 21:25   ` Marc Joliet
2018-01-07 21:53     ` Neil Bothwick

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='CAC=wYCHm1ufiDLpFi57u6pZXA06Q5X-nAG88sDyuzuhpzbgf+g@mail.gmail.com' \
    --to=adamcarter3@gmail.com \
    --cc=gentoo-user@lists.gentoo.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