| 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: Mon, 10 Sep 2018 18:26:08 +0000
From: "Schaufler, Casey" <casey.schaufler@...el.com>
To: Jiri Kosina <jikos@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
"Woodhouse, David" <dwmw@...zon.co.uk>,
Andi Kleen <ak@...ux.intel.com>,
Tim Chen <tim.c.chen@...ux.intel.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"Schaufler, Casey" <casey.schaufler@...el.com>
Subject: RE: [PATCH v5 1/2] x86/speculation: apply IBPB more strictly to
avoid cross-process data leak
> -----Original Message-----
> From: Jiri Kosina [mailto:jikos@...nel.org]
> Sent: Monday, September 10, 2018 2:24 AM
> To: Thomas Gleixner <tglx@...utronix.de>; Ingo Molnar <mingo@...hat.com>;
> Peter Zijlstra <peterz@...radead.org>; Josh Poimboeuf
> <jpoimboe@...hat.com>; Andrea Arcangeli <aarcange@...hat.com>;
> Woodhouse, David <dwmw@...zon.co.uk>; Andi Kleen <ak@...ux.intel.com>;
> Tim Chen <tim.c.chen@...ux.intel.com>; Schaufler, Casey
> <casey.schaufler@...el.com>
> Cc: linux-kernel@...r.kernel.org; x86@...nel.org
> Subject: [PATCH v5 1/2] x86/speculation: apply IBPB more strictly to avoid
> cross-process data leak
>
> From: Jiri Kosina <jkosina@...e.cz>
>
> Currently, we are issuing IBPB only in cases when switching into a non-
> dumpable
> process, the rationale being to protect such 'important and security sensitive'
> processess (such as GPG) from data leak into a different userspace process via
> spectre v2.
>
> This is however completely insufficient to provide proper userspace-to-
> userpace
> spectrev2 protection, as any process can poison branch buffers before being
> scheduled out, and the newly scheduled process immediately becomes
> spectrev2
> victim.
>
> In order to minimize the performance impact (for usecases that do require
> spectrev2 protection), issue the barrier only in cases when switching between
> processess where the victim can't be ptraced by the potential attacker (as in
> such cases, the attacker doesn't have to bother with branch buffers at all).
>
> Fixes: 18bf3c3ea8 ("x86/speculation: Use Indirect Branch Prediction Barrier in
> context switch")
> Originally-by: Tim Chen <tim.c.chen@...ux.intel.com>
> Signed-off-by: Jiri Kosina <jkosina@...e.cz>
> ---
> arch/x86/mm/tlb.c | 31 ++++++++++++++++++++-----------
> include/linux/ptrace.h | 4 ++++
> kernel/ptrace.c | 12 ++++++++----
> 3 files changed, 32 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/tlb.c
> index e96b99eb800c..ed4444402441 100644
> --- a/arch/x86/mm/tlb.c
> +++ b/arch/x86/mm/tlb.c
> @@ -7,6 +7,7 @@
> #include <linux/export.h>
> #include <linux/cpu.h>
> #include <linux/debugfs.h>
> +#include <linux/ptrace.h>
>
> #include <asm/tlbflush.h>
> #include <asm/mmu_context.h>
> @@ -180,6 +181,19 @@ static void sync_current_stack_to_mm(struct
> mm_struct *mm)
> }
> }
>
> +static bool ibpb_needed(struct task_struct *tsk, u64 last_ctx_id)
> +{
> + /*
> + * Check if the current (previous) task has access to the memory
> + * of the @tsk (next) task. If access is denied, make sure to
> + * issue a IBPB to stop user->user Spectre-v2 attacks.
> + *
> + * Note: __ptrace_may_access() returns 0 or -ERRNO.
> + */
> + return (tsk && tsk->mm && tsk->mm->context.ctx_id != last_ctx_id &&
> + __ptrace_may_access(tsk, PTRACE_MODE_IBPB));
> +}
> +
> void switch_mm_irqs_off(struct mm_struct *prev, struct mm_struct *next,
> struct task_struct *tsk)
> {
> @@ -262,18 +276,13 @@ void switch_mm_irqs_off(struct mm_struct *prev,
> struct mm_struct *next,
> * one process from doing Spectre-v2 attacks on another.
> *
> * As an optimization, flush indirect branches only when
> - * switching into processes that disable dumping. This
> - * protects high value processes like gpg, without having
> - * too high performance overhead. IBPB is *expensive*!
> - *
> - * This will not flush branches when switching into kernel
> - * threads. It will also not flush if we switch to idle
> - * thread and back to the same process. It will flush if we
> - * switch to a different non-dumpable process.
> + * switching into a processes that can't be ptrace by the
> + * current one (as in such case, attacker has much more
> + * convenient way how to tamper with the next process than
> + * branch buffer poisoning).
> */
> - if (tsk && tsk->mm &&
> - tsk->mm->context.ctx_id != last_ctx_id &&
> - get_dumpable(tsk->mm) != SUID_DUMP_USER)
> + if (static_cpu_has(X86_FEATURE_USE_IBPB) &&
> + ibpb_needed(tsk, last_ctx_id))
> indirect_branch_prediction_barrier();
>
> if (IS_ENABLED(CONFIG_VMAP_STACK)) {
> diff --git a/include/linux/ptrace.h b/include/linux/ptrace.h
> index 4f36431c380b..983d3f5545a8 100644
> --- a/include/linux/ptrace.h
> +++ b/include/linux/ptrace.h
> @@ -64,12 +64,15 @@ extern void exit_ptrace(struct task_struct *tracer,
> struct list_head *dead);
> #define PTRACE_MODE_NOAUDIT 0x04
> #define PTRACE_MODE_FSCREDS 0x08
> #define PTRACE_MODE_REALCREDS 0x10
> +#define PTRACE_MODE_NOACCESS_CHK 0x20
>
> /* shorthands for READ/ATTACH and FSCREDS/REALCREDS combinations */
> #define PTRACE_MODE_READ_FSCREDS (PTRACE_MODE_READ |
> PTRACE_MODE_FSCREDS)
> #define PTRACE_MODE_READ_REALCREDS (PTRACE_MODE_READ |
> PTRACE_MODE_REALCREDS)
> #define PTRACE_MODE_ATTACH_FSCREDS (PTRACE_MODE_ATTACH |
> PTRACE_MODE_FSCREDS)
> #define PTRACE_MODE_ATTACH_REALCREDS (PTRACE_MODE_ATTACH |
> PTRACE_MODE_REALCREDS)
> +#define PTRACE_MODE_IBPB (PTRACE_MODE_ATTACH |
> PTRACE_MODE_NOAUDIT \
> + | PTRACE_MODE_NOACCESS_CHK |
> PTRACE_MODE_REALCREDS)
>
> /**
> * ptrace_may_access - check whether the caller is permitted to access
> @@ -86,6 +89,7 @@ extern void exit_ptrace(struct task_struct *tracer, struct
> list_head *dead);
> * process_vm_writev or ptrace (and should use the real credentials).
> */
> extern bool ptrace_may_access(struct task_struct *task, unsigned int mode);
> +extern int __ptrace_may_access(struct task_struct *task, unsigned int mode);
>
> static inline int ptrace_reparented(struct task_struct *child)
> {
> diff --git a/kernel/ptrace.c b/kernel/ptrace.c
> index 21fec73d45d4..5c5e7cb597cd 100644
> --- a/kernel/ptrace.c
> +++ b/kernel/ptrace.c
> @@ -268,7 +268,7 @@ static int ptrace_has_cap(struct user_namespace *ns,
> unsigned int mode)
> }
>
> /* Returns 0 on success, -errno on denial. */
> -static int __ptrace_may_access(struct task_struct *task, unsigned int mode)
> +int __ptrace_may_access(struct task_struct *task, unsigned int mode)
> {
> const struct cred *cred = current_cred(), *tcred;
> struct mm_struct *mm;
> @@ -316,7 +316,8 @@ static int __ptrace_may_access(struct task_struct
> *task, unsigned int mode)
> gid_eq(caller_gid, tcred->sgid) &&
> gid_eq(caller_gid, tcred->gid))
> goto ok;
> - if (ptrace_has_cap(tcred->user_ns, mode))
> + if (!(mode & PTRACE_MODE_NOACCESS_CHK) &&
> + ptrace_has_cap(tcred->user_ns, mode))
> goto ok;
> rcu_read_unlock();
> return -EPERM;
> @@ -325,10 +326,13 @@ static int __ptrace_may_access(struct task_struct
> *task, unsigned int mode)
> mm = task->mm;
> if (mm &&
> ((get_dumpable(mm) != SUID_DUMP_USER) &&
> - !ptrace_has_cap(mm->user_ns, mode)))
> + ((mode & PTRACE_MODE_NOACCESS_CHK) ||
> + !ptrace_has_cap(mm->user_ns, mode))))
> return -EPERM;
>
> - return security_ptrace_access_check(task, mode);
> + if (!(mode & PTRACE_MODE_NOACCESS_CHK))
> + return security_ptrace_access_check(task, mode);
Why are you dropping the LSM check here, when in v4 you fixed the
SELinux audit locking issue? We can avoid introducing an LSM hook
and all the baggage around it if you can do the security_ptrace_access_check()
here.
> + return 0;
> }
>
> bool ptrace_may_access(struct task_struct *task, unsigned int mode)
>
> --
> Jiri Kosina
> SUSE Labs
Powered by blists - more mailing lists