[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190327115749.5770a102@gandalf.local.home>
Date: Wed, 27 Mar 2019 11:57:49 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Matthew Garrett <matthewgarrett@...gle.com>
Cc: jmorris@...ei.org, linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, dhowells@...hat.com,
linux-api@...r.kernel.org, luto@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
Matthew Garrett <mjg59@...gle.com>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org
Subject: Re: [PATCH V31 19/25] x86/mmiotrace: Lock down the testmmiotrace
module
On Tue, 26 Mar 2019 11:27:35 -0700
Matthew Garrett <matthewgarrett@...gle.com> wrote:
> 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. 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.
>
Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
I'm curious. Should there be a mode to lockdown the tracefs directory
too? As that can expose addresses.
-- Steve
> Suggested-by: Thomas Gleixner <tglx@...utronix.de>
> Signed-off-by: David Howells <dhowells@...hat.com
> Signed-off-by: Matthew Garrett <mjg59@...gle.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..9e8ad665f354 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", LOCKDOWN_INTEGRITY))
> + 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");
Powered by blists - more mailing lists