mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Kernel User <linux-kernel@riseup.net>
Cc: linux-kernel@vger.kernel.org, mhocko@suse.com, x86@kernel.org
Subject: Re: /sys/devices/system/cpu/vulnerabilities/ doesn't show all known CPU vulnerabilities
Date: Tue, 13 Aug 2019 23:21:15 +0200	[thread overview]
Message-ID: <20190813212115.GO16770@zn.tnic> (raw)
In-Reply-To: <20190813232829.3a1962cc@localhost>

On Tue, Aug 13, 2019 at 11:28:29PM +0300, Kernel User wrote:
> 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.
> 

You have to consider that some of those are addressed by a single
mitigation like MDS; the mitigation for others like lazy FPU restore
is not even present in /sys/devices/system/cpu/vulnerabilities/. Also,
depending on the CPU, some are not even affected.

So maintaining this in the kernel is unnecessary to say the least.

We could use a writeup somewhere which maps each vulnerability name -
and they're a gazillion by now - to the respective mitigation and what
is required but I'm not aware of such a writeup.

Documentation/admin-guide/hw-vuln/ could be a good start and
Documentation/admin-guide/hw-vuln/mds.rst could be a good example how
one should document the vulnerabilities and their mitigation. But that
would need to be exhaustive.

IMHO of course.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 20:28 Kernel User
2019-08-13 21:21 ` Borislav Petkov [this message]
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=20190813212115.GO16770@zn.tnic \
    --to=bp@alien8.de \
    --cc=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

all inboxes | Powered by JetHome®