From: Yann Droneaud <ydroneaud@opteya.com>
To: linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Yann Droneaud <ydroneaud@opteya.com>
Subject: [PATCH 4/3] binfmt/elf: don't expose prandom_u32() state
Date: Thu, 13 Jun 2019 15:39:46 +0200 [thread overview]
Message-ID: <20190613133946.20944-1-ydroneaud@opteya.com> (raw)
In-Reply-To: <cover.1560423331.git.ydroneaud@opteya.com>
Using prandom_u32() to get random offsets might expose fraction
of its internal state to userspace;
To prevent leaking prandom_u32() state, get_random_u32() could be
used instead, but with greater cost.
But it would be a big waste to call get_random_u32() to retrieve
only 4bits to 8bits at a time.
Instead this patch makes use of get_random_u64() to seed once a
local PRNG.
The local PRNG can be used safely to produces the random offsets,
exposing its internal state won't harm.
Link: https://lore.kernel.org/lkml/cover.1560423331.git.ydroneaud@opteya.com
Signed-off-by: Yann Droneaud <ydroneaud@opteya.com>
---
fs/binfmt_elf.c | 25 +++++++++++++++++++------
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index c84ef81f0639..9aaca1f671d1 100644
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -182,7 +182,8 @@ 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)
+static inline void elf_stack_randomize(unsigned long *pp,
+ struct rnd_state *state, size_t range)
{
u32 offset;
unsigned long p;
@@ -190,7 +191,7 @@ static inline void elf_stack_randomize(unsigned long *pp, size_t range)
if (!(current->flags & PF_RANDOMIZE))
return;
- offset = prandom_u32() % range;
+ offset = prandom_u32_state(state) % range;
p = *pp;
#ifdef CONFIG_STACK_GROWSUP
@@ -202,6 +203,15 @@ static inline void elf_stack_randomize(unsigned long *pp, size_t range)
*pp = p;
}
+static inline void elf_stack_randomize_seed(struct rnd_state *state)
+{
+ if (!(current->flags & PF_RANDOMIZE))
+ return;
+
+ prandom_seed_state(state,
+ get_random_u64());
+}
+
#ifndef ELF_BASE_PLATFORM
/*
* AT_BASE_PLATFORM indicates the "real" hardware/microarchitecture.
@@ -230,6 +240,9 @@ create_elf_tables(struct linux_binprm *bprm, struct elfhdr *exec,
int ei_index = 0;
const struct cred *cred = current_cred();
struct vm_area_struct *vma;
+ struct rnd_state state;
+
+ elf_stack_randomize_seed(&state);
/*
* In some cases (e.g. Hyper-Threading), we want to avoid L1
@@ -239,7 +252,7 @@ create_elf_tables(struct linux_binprm *bprm, struct elfhdr *exec,
p = arch_align_stack(p);
- elf_stack_randomize(&p, 256);
+ elf_stack_randomize(&p, &state, 256);
elf_stack_align(&p);
/*
@@ -260,7 +273,7 @@ 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);
+ elf_stack_randomize(&p, &state, 16);
u_platform = elf_stack_alloc(&p, len);
if (__copy_to_user(u_platform, k_platform, len))
@@ -275,14 +288,14 @@ 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);
+ elf_stack_randomize(&p, &state, 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_randomize(&p, &state, 256);
elf_stack_align(&p);
/* Create the ELF interpreter info */
--
2.21.0
prev parent reply other threads:[~2019-06-13 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 11:26 [PATCH 0/3] ELF interpretor info: align and add random padding Yann Droneaud
2019-06-13 11:26 ` [PATCH 1/3] binfmt/elf: use functions for stack manipulation Yann Droneaud
2019-06-13 11:26 ` [PATCH 2/3] binfmt/elf: align AT_RANDOM array Yann Droneaud
2019-06-13 11:26 ` [PATCH 3/3] binfmt/elf: randomize padding between ELF interp info Yann Droneaud
2019-06-13 13:39 ` Yann Droneaud [this message]
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=20190613133946.20944-1-ydroneaud@opteya.com \
--to=ydroneaud@opteya.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).