| 1 | ===================
|
| 2 | Speculation Control
|
| 3 | ===================
|
| 4 |
|
| 5 | Quite some CPUs have speculation-related misfeatures which are in
|
| 6 | fact vulnerabilities causing data leaks in various forms even across
|
| 7 | privilege domains.
|
| 8 |
|
| 9 | The kernel provides mitigation for such vulnerabilities in various
|
| 10 | forms. Some of these mitigations are compile-time configurable and some
|
| 11 | can be supplied on the kernel command line.
|
| 12 |
|
| 13 | There is also a class of mitigations which are very expensive, but they can
|
| 14 | be restricted to a certain set of processes or tasks in controlled
|
| 15 | environments. The mechanism to control these mitigations is via
|
| 16 | :manpage:`prctl(2)`.
|
| 17 |
|
| 18 | There are two prctl options which are related to this:
|
| 19 |
|
| 20 | * PR_GET_SPECULATION_CTRL
|
| 21 |
|
| 22 | * PR_SET_SPECULATION_CTRL
|
| 23 |
|
| 24 | PR_GET_SPECULATION_CTRL
|
| 25 | -----------------------
|
| 26 |
|
| 27 | PR_GET_SPECULATION_CTRL returns the state of the speculation misfeature
|
| 28 | which is selected with arg2 of prctl(2). The return value uses bits 0-3 with
|
| 29 | the following meaning (with the caveat that PR_SPEC_L1D_FLUSH has less obvious
|
| 30 | semantics, see documentation for that specific control below):
|
| 31 |
|
| 32 | ==== ====================== ==================================================
|
| 33 | Bit Define Description
|
| 34 | ==== ====================== ==================================================
|
| 35 | 0 PR_SPEC_PRCTL Mitigation can be controlled per task by
|
| 36 | PR_SET_SPECULATION_CTRL.
|
| 37 | 1 PR_SPEC_ENABLE The speculation feature is enabled, mitigation is
|
| 38 | disabled.
|
| 39 | 2 PR_SPEC_DISABLE The speculation feature is disabled, mitigation is
|
| 40 | enabled.
|
| 41 | 3 PR_SPEC_FORCE_DISABLE Same as PR_SPEC_DISABLE, but cannot be undone. A
|
| 42 | subsequent prctl(..., PR_SPEC_ENABLE) will fail.
|
| 43 | 4 PR_SPEC_DISABLE_NOEXEC Same as PR_SPEC_DISABLE, but the state will be
|
| 44 | cleared on :manpage:`execve(2)`.
|
| 45 | ==== ====================== ==================================================
|
| 46 |
|
| 47 | If all bits are 0 the CPU is not affected by the speculation misfeature.
|
| 48 |
|
| 49 | If PR_SPEC_PRCTL is set, then the per-task control of the mitigation is
|
| 50 | available. If not set, prctl(PR_SET_SPECULATION_CTRL) for the speculation
|
| 51 | misfeature will fail.
|
| 52 |
|
| 53 | .. _set_spec_ctrl:
|
| 54 |
|
| 55 | PR_SET_SPECULATION_CTRL
|
| 56 | -----------------------
|
| 57 |
|
| 58 | PR_SET_SPECULATION_CTRL allows to control the speculation misfeature, which
|
| 59 | is selected by arg2 of :manpage:`prctl(2)` per task. arg3 is used to hand
|
| 60 | in the control value, i.e. either PR_SPEC_ENABLE or PR_SPEC_DISABLE or
|
| 61 | PR_SPEC_FORCE_DISABLE.
|
| 62 |
|
| 63 | Common error codes
|
| 64 | ------------------
|
| 65 | ======= =================================================================
|
| 66 | Value Meaning
|
| 67 | ======= =================================================================
|
| 68 | EINVAL The prctl is not implemented by the architecture or unused
|
| 69 | prctl(2) arguments are not 0.
|
| 70 |
|
| 71 | ENODEV arg2 is selecting a not supported speculation misfeature.
|
| 72 | ======= =================================================================
|
| 73 |
|
| 74 | PR_SET_SPECULATION_CTRL error codes
|
| 75 | -----------------------------------
|
| 76 | ======= =================================================================
|
| 77 | Value Meaning
|
| 78 | ======= =================================================================
|
| 79 | 0 Success
|
| 80 |
|
| 81 | ERANGE arg3 is incorrect, i.e. it's neither PR_SPEC_ENABLE nor
|
| 82 | PR_SPEC_DISABLE nor PR_SPEC_FORCE_DISABLE.
|
| 83 |
|
| 84 | ENXIO For PR_SPEC_STORE_BYPASS: control of the selected speculation misfeature
|
| 85 | is not possible via prctl, because of the system's boot configuration.
|
| 86 |
|
| 87 | EPERM Speculation was disabled with PR_SPEC_FORCE_DISABLE and caller tried to
|
| 88 | enable it again.
|
| 89 |
|
| 90 | EPERM For PR_SPEC_L1D_FLUSH and PR_SPEC_INDIRECT_BRANCH: control of the
|
| 91 | mitigation is not possible because of the system's boot configuration.
|
| 92 |
|
| 93 | ======= =================================================================
|
| 94 |
|
| 95 | Speculation misfeature controls
|
| 96 | -------------------------------
|
| 97 | - PR_SPEC_STORE_BYPASS: Speculative Store Bypass
|
| 98 |
|
| 99 | Invocations:
|
| 100 | * prctl(PR_GET_SPECULATION_CTRL, PR_SPEC_STORE_BYPASS, 0, 0, 0);
|
| 101 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_STORE_BYPASS, PR_SPEC_ENABLE, 0, 0);
|
| 102 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_STORE_BYPASS, PR_SPEC_DISABLE, 0, 0);
|
| 103 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_STORE_BYPASS, PR_SPEC_FORCE_DISABLE, 0, 0);
|
| 104 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_STORE_BYPASS, PR_SPEC_DISABLE_NOEXEC, 0, 0);
|
| 105 |
|
| 106 | - PR_SPEC_INDIR_BRANCH: Indirect Branch Speculation in User Processes
|
| 107 | (Mitigate Spectre V2 style attacks against user processes)
|
| 108 |
|
| 109 | Invocations:
|
| 110 | * prctl(PR_GET_SPECULATION_CTRL, PR_SPEC_INDIRECT_BRANCH, 0, 0, 0);
|
| 111 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_INDIRECT_BRANCH, PR_SPEC_ENABLE, 0, 0);
|
| 112 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_INDIRECT_BRANCH, PR_SPEC_DISABLE, 0, 0);
|
| 113 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_INDIRECT_BRANCH, PR_SPEC_FORCE_DISABLE, 0, 0);
|
| 114 |
|
| 115 | - PR_SPEC_L1D_FLUSH: Flush L1D Cache on context switch out of the task
|
| 116 | (works only when tasks run on non SMT cores)
|
| 117 |
|
| 118 | For this control, PR_SPEC_ENABLE means that the **mitigation** is enabled (L1D
|
| 119 | is flushed), PR_SPEC_DISABLE means it is disabled.
|
| 120 |
|
| 121 | Invocations:
|
| 122 | * prctl(PR_GET_SPECULATION_CTRL, PR_SPEC_L1D_FLUSH, 0, 0, 0);
|
| 123 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_L1D_FLUSH, PR_SPEC_ENABLE, 0, 0);
|
| 124 | * prctl(PR_SET_SPECULATION_CTRL, PR_SPEC_L1D_FLUSH, PR_SPEC_DISABLE, 0, 0);
|