[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <cbabb2af40e5f0bdb516cf07aea6e8269d1df89a.1560423331.git.ydroneaud@opteya.com>
Date: Thu, 13 Jun 2019 13:26:06 +0200
From: Yann Droneaud <ydroneaud@...eya.com>
To: linux-kernel@...r.kernel.org,
kernel-hardening@...ts.openwall.com
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Yann Droneaud <ydroneaud@...eya.com>,
Elena Reshetova <elena.reshetova@...el.com>
Subject: [PATCH 3/3] binfmt/elf: randomize padding between ELF interp info
As AT_RANDOM is on top of the stack, retrieving AT_RANDOM value
through getauxval() could help, if needed, an attacker accesses
interesting locations in program stack, if offset from top of the
stack is fixed/known beforehand.
As a pure cargo-cult feature, inspired by "x86/entry/64: randomize
kernel stack offset upon syscall" [1], this patch adds small
random offsets between the top of the stack, AT_RANDOM array,
AT_PLAFORM strings, AT_BASE_PLATFORM strings, and the auxiliary
vector (aka. ELF interpretor info)
It introduces 16 possible different locations for AT_RANDOM array,
16 possible different locations for AT_PLATFORM, same for AT_BASE_PLATFORM,
and 16 more for the auxiliary vector.
Thus, at most 544 bytes (256 + 16 + 16 + 256) can be wasted in
padding.
This patch also enforces an 16bytes aligned AT_RANDOM array as
elf_stack_align() is used, regardless of arch_align_stack().
It should be noted, per ABI, it's not possible to insert random
padding between auxiliary vector and environment variables, nor
between environment variables and program arguments, nor before
programs arguments. (It should be possible to shuffle values
within auxillay and environment variables, if someone want to
scare userspace).
[1] https://www.openwall.com/lists/kernel-hardening/2019/03/29/3
Link: https://lore.kernel.org/lkml/cover.1560423331.git.ydroneaud@opteya.com
Cc: Elena Reshetova <elena.reshetova@...el.com>
Signed-off-by: Yann Droneaud <ydroneaud@...eya.com>
---
fs/binfmt_elf.c | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index cfcc01fff4ae..c84ef81f0639 100644
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -182,6 +182,26 @@ static inline elf_addr_t __user *elf_stack_alloc(unsigned long *pp,
return sp;
}
+static inline void elf_stack_randomize(unsigned long *pp, size_t range)
+{
+ u32 offset;
+ unsigned long p;
+
+ if (!(current->flags & PF_RANDOMIZE))
+ return;
+
+ offset = prandom_u32() % range;
+ p = *pp;
+
+#ifdef CONFIG_STACK_GROWSUP
+ p += offset;
+#else
+ p -= offset;
+#endif
+
+ *pp = p;
+}
+
#ifndef ELF_BASE_PLATFORM
/*
* AT_BASE_PLATFORM indicates the "real" hardware/microarchitecture.
@@ -219,6 +239,9 @@ create_elf_tables(struct linux_binprm *bprm, struct elfhdr *exec,
p = arch_align_stack(p);
+ elf_stack_randomize(&p, 256);
+ elf_stack_align(&p);
+
/*
* Generate 16 random bytes for userspace PRNG seeding.
*/
@@ -237,6 +260,8 @@ create_elf_tables(struct linux_binprm *bprm, struct elfhdr *exec,
if (k_platform) {
size_t len = strlen(k_platform) + 1;
+ elf_stack_randomize(&p, 16);
+
u_platform = elf_stack_alloc(&p, len);
if (__copy_to_user(u_platform, k_platform, len))
return -EFAULT;
@@ -250,11 +275,16 @@ create_elf_tables(struct linux_binprm *bprm, struct elfhdr *exec,
if (k_base_platform) {
size_t len = strlen(k_base_platform) + 1;
+ elf_stack_randomize(&p, 16);
+
u_base_platform = elf_stack_alloc(&p, len);
if (__copy_to_user(u_base_platform, k_base_platform, len))
return -EFAULT;
}
+ elf_stack_randomize(&p, 256);
+ elf_stack_align(&p);
+
/* Create the ELF interpreter info */
elf_info = (elf_addr_t *)current->mm->saved_auxv;
/* update AT_VECTOR_SIZE_BASE if the number of NEW_AUX_ENT() changes */
--
2.21.0
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.
