linux-kernel - Re: /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 15 Aug 2019 22:37:30 +0300
From:   Kernel User <linux-kernel@...eup.net>
To:     linux-kernel@...r.kernel.org
Cc:     mhocko@...e.com, x86@...nel.org
Subject: Re: /sys/devices/system/cpu/vulnerabilities/ doesn't show all known
 CPU vulnerabilities

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.