All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kernel User <linux-kernel@riseup.net>
To: linux-kernel@vger.kernel.org
Cc: mhocko@suse.com, x86@kernel.org
Subject: /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities
Date: Tue, 13 Aug 2019 23:28:29 +0300	[thread overview]
Message-ID: <20190813232829.3a1962cc@localhost> (raw)

Hi,

'ls /sys/devices/system/cpu/vulnerabilities/' doesn't show all known
CPU vulnerabilities and their variants. Only some of them:

l1tf  mds  meltdown  spec_store_bypass  spectre_v1  spectre_v2

Wikipedia shows more variants:

https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)#Speculative_execution_security_vulnerabilities

It would be good to have a full list with statuses. Then one won't need to use external (potentially non-safe) tools like https://github.com/speed47/spectre-meltdown-checker to find out the vulnerabilities of a system.


This started as a feature request on openSUSE's bugzilla where it was
suggested to report it here:

http://bugzilla.suse.com/show_bug.cgi?id=1145191

             reply	other threads:[~2019-08-13 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 20:28 Kernel User [this message]
2019-08-13 21:21 ` /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities 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
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=20190813232829.3a1962cc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.