path: root/security/lockdown/lockdown.c
diff options
authorDavid Howells <>2019-08-19 17:17:56 -0700
committerJames Morris <>2019-08-19 21:54:16 -0700
commit906357f77a077508d160e729f917c5f0a4304f25 (patch)
tree049ecdbb02af347886a383126722b6bc853503a6 /security/lockdown/lockdown.c
parent20657f66ef52e5005369e4ef539d4cbf01eab10d (diff)
x86/mmiotrace: Lock down the testmmiotrace module
The testmmiotrace module shouldn't be permitted when the kernel is locked down as it can be used to arbitrarily read and write MMIO space. This is a runtime check rather than buildtime in order to allow configurations where the same kernel may be run in both locked down or permissive modes depending on local policy. Suggested-by: Thomas Gleixner <> Signed-off-by: David Howells < Signed-off-by: Matthew Garrett <> Acked-by: Steven Rostedt (VMware) <> Reviewed-by: Kees Cook <> cc: Thomas Gleixner <> cc: Steven Rostedt <> cc: Ingo Molnar <> cc: "H. Peter Anvin" <> cc: Signed-off-by: James Morris <>
Diffstat (limited to 'security/lockdown/lockdown.c')
1 files changed, 1 insertions, 0 deletions
diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c
index 0fa434294667..2eadbe0667e7 100644
--- a/security/lockdown/lockdown.c
+++ b/security/lockdown/lockdown.c
@@ -29,6 +29,7 @@ static char *lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1] = {
[LOCKDOWN_PCMCIA_CIS] = "direct PCMCIA CIS storage",
[LOCKDOWN_TIOCSSERIAL] = "reconfiguration of serial port IO",
[LOCKDOWN_MODULE_PARAMETERS] = "unsafe module parameters",
+ [LOCKDOWN_MMIOTRACE] = "unsafe mmio",