lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 28 Feb 2019 15:11:57 -0800 From: Matthew Garrett <matthewgarrett@...gle.com> To: jmorris@...ei.org Cc: linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org, dhowells@...hat.com Subject: [PATCH 21/27] x86/mmiotrace: Lock down the testmmiotrace module From: David Howells <dhowells@...hat.com> 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. Suggested-by: Thomas Gleixner <tglx@...utronix.de> Signed-off-by: David Howells <dhowells@...hat.com cc: Thomas Gleixner <tglx@...utronix.de> cc: Steven Rostedt <rostedt@...dmis.org> cc: Ingo Molnar <mingo@...nel.org> cc: "H. Peter Anvin" <hpa@...or.com> cc: x86@...nel.org --- arch/x86/mm/testmmiotrace.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/x86/mm/testmmiotrace.c b/arch/x86/mm/testmmiotrace.c index f6ae6830b341..bbaad357f5d7 100644 --- a/arch/x86/mm/testmmiotrace.c +++ b/arch/x86/mm/testmmiotrace.c @@ -115,6 +115,9 @@ static int __init init(void) { unsigned long size = (read_far) ? (8 << 20) : (16 << 10); + if (kernel_is_locked_down("MMIO trace testing")) + return -EPERM; + if (mmio_address == 0) { pr_err("you have to use the module argument mmio_address.\n"); pr_err("DO NOT LOAD THIS MODULE UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!\n"); -- 2.21.0.352.gf09ad66450-goog
Powered by blists - more mailing lists