Skip to content

Flawed usage of mitigations=auto,nosmt #17

Open

Description

@raja-grewal

I noticed that when it comes to kernel command line options for CPU vulnerability mitigations there is only following:

# Mitigates all known CPU vulnerabilities, disabling SMT *if needed*.
mitigations=auto,nosmt

While this a very convenient and efficient way to enable them, there is an apparent flaw in this approach I have discussed here Kicksecure/security-misc#199 (comment) which I would like to bring to everyone's attention.

In short, this usage is incomplete as the two parameters together do not perform maximum hardening by default.

Using the kernel docs as a guide we can find several others that can be tightened as I have noted in the Kicksecure issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions