public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Kees Cook <kees@kernel.org>
Cc: <linux@armlinux.org.uk>, <ardb@kernel.org>, <arnd@arndb.de>,
	<afd@ti.com>, <akpm@linux-foundation.org>,
	<rmk+kernel@armlinux.org.uk>, <linus.walleij@linaro.org>,
	<eric.devolder@oracle.com>, <robh@kernel.org>,
	<masahiroy@kernel.org>, <palmer@rivosinc.com>,
	<samitolvanen@google.com>, <xiao.w.wang@intel.com>,
	<alexghiti@rivosinc.com>, <nathan@kernel.org>,
	<jan.kiszka@siemens.com>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-efi@vger.kernel.org>,
	Alexander Popov <alex.popov@linux.com>
Subject: Re: [PATCH] ARM: Add support for STACKLEAK gcc plugin
Date: Fri, 21 Jun 2024 10:24:52 +0800	[thread overview]
Message-ID: <bb1ea7f5-973d-54cf-36ab-fe4d55c1b5bc@huawei.com> (raw)
In-Reply-To: <202406201136.A441E0B7@keescook>



On 2024/6/21 2:38, Kees Cook wrote:
> On Thu, Jun 20, 2024 at 09:16:49PM +0800, Jinjie Ruan wrote:
>> Add the STACKLEAK gcc plugin to arm32 by adding the helper used by
>> stackleak common code: on_thread_stack(). It initialize the stack with the
>> poison value before returning from system calls which improves the kernel
>> security. Additionally, this disables the plugin in EFI stub code and
>> decompress code, which are out of scope for the protection.
> 
> Oh very cool! Thanks for sending this!
> 
>> Before the test on Qemu versatilepb board:
>> 	# echo STACKLEAK_ERASING  > /sys/kernel/debug/provoke-crash/DIRECT
>> 	lkdtm: Performing direct entry STACKLEAK_ERASING
>> 	lkdtm: XFAIL: stackleak is not supported on this arch (HAVE_ARCH_STACKLEAK=n)
>>
>> After:
>> 	# echo STACKLEAK_ERASING  > /sys/kernel/debug/provoke-crash/DIRECT
>> 	lkdtm: Performing direct entry STACKLEAK_ERASING
>> 	lkdtm: stackleak stack usage:
>> 	  high offset: 80 bytes
>> 	  current:     280 bytes
>> 	  lowest:      696 bytes
>> 	  tracked:     696 bytes
>> 	  untracked:   192 bytes
>> 	  poisoned:    7220 bytes
>> 	  low offset:  4 bytes
>> 	lkdtm: OK: the rest of the thread stack is properly erased
>>
>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>> ---
>>  arch/arm/Kconfig                      | 1 +
>>  arch/arm/boot/compressed/Makefile     | 1 +
>>  arch/arm/include/asm/stacktrace.h     | 5 +++++
>>  arch/arm/kernel/entry-common.S        | 3 +++
>>  drivers/firmware/efi/libstub/Makefile | 3 ++-
>>  5 files changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>> index 036381c5d42f..b211b7f5a138 100644
>> --- a/arch/arm/Kconfig
>> +++ b/arch/arm/Kconfig
>> @@ -86,6 +86,7 @@ config ARM
>>  	select HAVE_ARCH_PFN_VALID
>>  	select HAVE_ARCH_SECCOMP
>>  	select HAVE_ARCH_SECCOMP_FILTER if AEABI && !OABI_COMPAT
>> +	select HAVE_ARCH_STACKLEAK
>>  	select HAVE_ARCH_THREAD_STRUCT_WHITELIST
>>  	select HAVE_ARCH_TRACEHOOK
>>  	select HAVE_ARCH_TRANSPARENT_HUGEPAGE if ARM_LPAE
>> diff --git a/arch/arm/boot/compressed/Makefile b/arch/arm/boot/compressed/Makefile
>> index 6bca03c0c7f0..945b5975fce2 100644
>> --- a/arch/arm/boot/compressed/Makefile
>> +++ b/arch/arm/boot/compressed/Makefile
>> @@ -9,6 +9,7 @@ OBJS		=
>>  
>>  HEAD	= head.o
>>  OBJS	+= misc.o decompress.o
>> +CFLAGS_decompress.o += $(DISABLE_STACKLEAK_PLUGIN)
>>  ifeq ($(CONFIG_DEBUG_UNCOMPRESS),y)
>>  OBJS	+= debug.o
>>  AFLAGS_head.o += -DDEBUG
>> diff --git a/arch/arm/include/asm/stacktrace.h b/arch/arm/include/asm/stacktrace.h
>> index 360f0d2406bf..a9b4b72ed241 100644
>> --- a/arch/arm/include/asm/stacktrace.h
>> +++ b/arch/arm/include/asm/stacktrace.h
>> @@ -26,6 +26,11 @@ struct stackframe {
>>  #endif
>>  };
>>  
>> +static inline bool on_thread_stack(void)
>> +{
>> +	return !(((unsigned long)(current->stack) ^ current_stack_pointer) & ~(THREAD_SIZE - 1));
>> +}
>> +
>>  static __always_inline
>>  void arm_get_current_stackframe(struct pt_regs *regs, struct stackframe *frame)
>>  {
>> diff --git a/arch/arm/kernel/entry-common.S b/arch/arm/kernel/entry-common.S
>> index 5c31e9de7a60..f379c852dcb7 100644
>> --- a/arch/arm/kernel/entry-common.S
>> +++ b/arch/arm/kernel/entry-common.S
>> @@ -119,6 +119,9 @@ no_work_pending:
>>  
>>  	ct_user_enter save = 0
>>  
>> +#ifdef CONFIG_GCC_PLUGIN_STACKLEAK
>> +	bl	stackleak_erase_on_task_stack
>> +#endif
>>  	restore_user_regs fast = 0, offset = 0
>>  ENDPROC(ret_to_user_from_irq)
>>  ENDPROC(ret_to_user)
>> diff --git a/drivers/firmware/efi/libstub/Makefile b/drivers/firmware/efi/libstub/Makefile
>> index 06f0428a723c..20d8a491f25f 100644
>> --- a/drivers/firmware/efi/libstub/Makefile
>> +++ b/drivers/firmware/efi/libstub/Makefile
>> @@ -27,7 +27,8 @@ cflags-$(CONFIG_ARM64)		+= -fpie $(DISABLE_STACKLEAK_PLUGIN) \
>>  cflags-$(CONFIG_ARM)		+= -DEFI_HAVE_STRLEN -DEFI_HAVE_STRNLEN \
>>  				   -DEFI_HAVE_MEMCHR -DEFI_HAVE_STRRCHR \
>>  				   -DEFI_HAVE_STRCMP -fno-builtin -fpic \
>> -				   $(call cc-option,-mno-single-pic-base)
>> +				   $(call cc-option,-mno-single-pic-base) \
>> +				   $(DISABLE_STACKLEAK_PLUGIN)
>>  cflags-$(CONFIG_RISCV)		+= -fpic -DNO_ALTERNATIVE -mno-relax
>>  cflags-$(CONFIG_LOONGARCH)	+= -fpie
> 
> This looks very straight forward! If an ARM person can Ack this, I could
> carry it via the hardening tree. Otherwise, it should probably go via
> rmk's patch tracker?

Thank you for your attention and reply.

> 
> -Kees
> 


  reply	other threads:[~2024-06-21  2:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 13:16 [PATCH] ARM: Add support for STACKLEAK gcc plugin Jinjie Ruan
2024-06-20 18:38 ` Kees Cook
2024-06-21  2:24   ` Jinjie Ruan [this message]
2024-06-21 11:00 ` Ard Biesheuvel

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=bb1ea7f5-973d-54cf-36ab-fe4d55c1b5bc@huawei.com \
    --to=ruanjinjie@huawei.com \
    --cc=afd@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.popov@linux.com \
    --cc=alexghiti@rivosinc.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=eric.devolder@oracle.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kees@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=palmer@rivosinc.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robh@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=xiao.w.wang@intel.com \
    /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