From: David Howells <dhowells@redhat.com>
To: rostedt@goodmis.org
Cc: dhowells@redhat.com, mingo@redhat.com,
alexei.starovoitov@gmail.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC][PATCH] Lock down ftrace
Date: Thu, 09 Nov 2017 16:42:12 +0000 [thread overview]
Message-ID: <11100.1510245732@warthog.procyon.org.uk> (raw)
Hi,
I (may) need to lock down ftrace under secure boot conditions as part of the
patch series that can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=efi-lock-down
Can you tell me that if the attached patch is sufficient to the cause?
Thanks,
David
---
commit 3fb4590c0ad0a751b2090c489df79193510e6aaa
Author: David Howells <dhowells@redhat.com>
Date: Wed Nov 8 15:41:02 2017 +0000
Lock down ftrace
Disallow the use of ftrace when the kernel is locked down. This patch
turns off ftrace_enabled late in the kernel boot so that the selftest can
still be potentially be run.
The sysctl that controls ftrace_enables is also disallowed when the kernel
is locked down. If the lockdown is lifted, then the sysctl can be used to
reenable ftrace - if ftrace was compiled with CONFIG_DYNAMIC_FTRACE, that
is; if it wasn't then it won't be possible to reenable it.
This prevents crypto data theft by analysis of execution patterns, and, if
in future ftrace also logs the register contents at the time, will prevent
data theft by that mechanism also.
Reported-by: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Signed-off-by: David Howells <dhowells@redhat.com>
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 6abfafd7f173..9c7135963d80 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -6508,6 +6508,9 @@ ftrace_enable_sysctl(struct ctl_table *table, int write,
{
int ret = -ENODEV;
+ if (kernel_is_locked_down("Use of ftrace"))
+ return -EPERM;
+
mutex_lock(&ftrace_lock);
if (unlikely(ftrace_disabled))
@@ -6896,3 +6899,22 @@ void ftrace_graph_exit_task(struct task_struct *t)
kfree(ret_stack);
}
#endif
+
+#ifdef CONFIG_LOCK_DOWN_KERNEL
+static int __init ftrace_lock_down(void)
+{
+ mutex_lock(&ftrace_lock);
+
+ if (!ftrace_disabled && ftrace_enabled &&
+ kernel_is_locked_down("Use of ftrace")) {
+ ftrace_enabled = false;
+ last_ftrace_enabled = false;
+ ftrace_trace_function = ftrace_stub;
+ ftrace_shutdown_sysctl();
+ }
+
+ mutex_unlock(&ftrace_lock);
+ return 0;
+}
+late_initcall(ftrace_lock_down);
+#endif
next reply other threads:[~2017-11-09 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 16:42 David Howells [this message]
2017-11-09 18:03 ` Steven Rostedt
2017-11-09 21:54 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11100.1510245732@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®