From: Kernel User <linux-kernel@riseup.net>
To: linux-kernel@vger.kernel.org
Cc: mhocko@suse.com, x86@kernel.org
Subject: Re: /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities
Date: Thu, 15 Aug 2019 22:37:30 +0300 [thread overview]
Message-ID: <20190815223730.0b5c6c13@localhost> (raw)
In-Reply-To: <alpine.DEB.2.21.1908151054090.2241@nanos.tec.linutronix.de>
On Thu, 15 Aug 2019 11:03:35 +0200 (CEST) Thomas Gleixner wrote:
> It's used to denote vulnerability classes and their mitigations:
>
> - Spectre v1
> - Spectre v2
> - Meltdown
> - SSB
> - L1TF
> - MDS
In the Wikipedia article there are:
+ Bounds Check Bypass (Spectre, Variant 1)
+ Branch Target Injection (Spectre, Variant 2)
+ Rogue Data Cache Load (Meltdown, Variant 3)
- Rogue System Register Read (Spectre-NG, Variant 3a)
+ Speculative Store Bypass (Spectre-NG, Variant 4)
- Lazy FP state restore (Spectre-NG)
- Bounds Check Bypass Store (Spectre-NG)
+ Foreshadow
- Spoiler
+ Microarchitectural Data Sampling
I have marked with '+' those which I recognize in the list you provided
and with '-' those which are not.
> We are not tracking subclasses and their individual CVEs.
Why do you say that? In your list only L1TF and MDS are not subclasses,
i.e. subclasses are in the list. So why not have the others? Also
Spoiler seems to be a separate class.
next prev parent reply other threads:[~2019-08-15 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 20:28 /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities Kernel User
2019-08-13 21:21 ` Borislav Petkov
2019-08-13 22:00 ` Kernel User
2019-08-14 7:04 ` Borislav Petkov
2019-08-14 9:11 ` Kernel User
2019-08-15 9:03 ` Thomas Gleixner
2019-08-15 19:37 ` Kernel User [this message]
2019-08-15 20:04 ` Thomas Gleixner
2019-08-17 20:41 ` Kernel User
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=20190815223730.0b5c6c13@localhost \
--to=linux-kernel@riseup.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=x86@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