[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 30 Mar 2017 09:32:00 +0100
From: James Morse <james.morse@....com>
To: Keun-O Park <kpark3469@...il.com>
CC: kernel-hardening@...ts.openwall.com,
linux-arm-kernel@...ts.infradead.org, Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>,
Kees Cook <keescook@...omium.org>, Mark Rutland <mark.rutland@....com>,
Pratyush Anand <panand@...hat.com>,
keun-o.park@...kmatter.ae
Subject: Re: [PATCH v4 3/3] arm64/uaccess: Add hardened
usercopy check for bad stack accesses
Hi,
On 17/02/17 18:09, Keun-O Park wrote:
>> diff --git a/arch/arm64/include/asm/uaccess.h b/arch/arm64/include/asm/uaccess.h
>> index 46da3ea638bb..d3494840a61c 100644
>> --- a/arch/arm64/include/asm/uaccess.h
>> +++ b/arch/arm64/include/asm/uaccess.h
>> @@ -356,6 +356,22 @@ do { \
>> +static inline void check_obj_in_unused_stack(const void *obj, unsigned long len)
>> +{
>> + unsigned long stack = (unsigned long)task_stack_page(current);
>> +
>> + if (__builtin_constant_p(len) || !IS_ENABLED(CONFIG_HARDENED_USERCOPY) || !len)
>> + return;
>> +
>> + /*
>> + * If current_stack_pointer is on the task stack, obj must not lie
>> + * between current_stack_pointer and the last stack address.
>> + */
>> + if ((current_stack_pointer & ~(THREAD_SIZE-1)) == stack)
>> + BUG_ON(stack <= (unsigned long)obj &&
>> + (unsigned long)obj < current_stack_pointer);
>> +}
>> +
>
> It looks to me that this function is just doing the similar check that
> check_stack_object() may do.
> Probably I guess you had a problem in checking the correct fp of
> caller's function while you tried to use walk_stackframe().
The value needs to be taken in a hopefully-inlined function if you want to catch
LKDTMs 'just off the stack' writes. Doing it like this saved meddling with the
generic code.
> Instead of creating check_obj_in_unused_stack(), how about handing
> over current_stack_pointer to check_stack_object();
Sure, do you want to give this a go? (I have my hands full at the moment)
It might not be the right check on all architectures, x86 redzone comes to mind,
but it doesn't look like they use this in the kernel.
There is also Al Viro's uaccess unification work that may affect whether this is
worth doing now:
https://lkml.org/lkml/2015/12/3/494
Thanks,
James
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
