mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: david.keisarschm@mail.huji.ac.il
To: linux-kernel@vger.kernel.org
Cc: Jason@zx2c4.com,
	David Keisar Schmidt <david.keisarschm@mail.huji.ac.il>,
	aksecurity@gmail.com, ilay.bahat1@gmail.com, bpf@vger.kernel.org
Subject: [PATCH v3 0/3] Replace invocations of prandom_u32() with get_random_u32()
Date: Sun, 18 Dec 2022 20:18:57 +0200	[thread overview]
Message-ID: <cover.1671277662.git.david.keisarschm@mail.huji.ac.il> (raw)

From: David Keisar Schmidt <david.keisarschm@mail.huji.ac.il>

Hi,

This third series add some changes to the commit messages,
and also replaces get_random_u32 with get_random_u32_below,
in a case a modulo operation is done on the result.

The security improvements for prandom_u32 done in commits c51f8f88d705
from October 2020 and d4150779e60f from May 2022 didn't handle the cases
when prandom_bytes_state() and prandom_u32_state() are used.

Specifically, this weak randomization takes place in three cases:
    1.	mm/slab.c
    2.	mm/slab_common.c
    3.	arch/x86/mm/kaslr.c

The first two invocations (mm/slab.c, mm/slab_common.c) are used to create
randomization in the slab allocator freelists.
This is done to make sure attackers can’t obtain information on the heap state.

The last invocation, inside arch/x86/mm/kaslr.c,
randomizes the virtual address space of kernel memory regions.
Hence, we have added the necessary changes to make those randomizations stronger,
switching  prandom_u32 instances to get_random_u32.

# Changes since v2

* edited commit message in all three patches.
* replaced instances of get_random_u32 with get_random_u32_below
    in mm/slab.c, mm/slab_common.c

# Changes since v1

* omitted the renaming patch, per the feedback we received
* omitted the replace of prandom_u32_state with get_random_u32 in bpf/core.c
 as it turned out to be a duplicate of a patch suggested earlier by Jason Donenfeld

Regards,


David Keisar Schmidt (3):
  Replace invocation of weak PRNG in mm/slab.c
  Replace invocation of weak PRNG inside mm/slab_common.c
  Replace invocation of weak PRNG in arch/x86/mm/kaslr.c

 arch/x86/mm/kaslr.c |  5 +----
 mm/slab.c           | 25 ++++++++++---------------
 mm/slab_common.c    | 11 +++--------
 3 files changed, 14 insertions(+), 27 deletions(-)

-- 
2.38.0


             reply	other threads:[~2022-12-18 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18 18:18 david.keisarschm [this message]
2022-12-18 18:18 ` [PATCH v3 1/3] Replace invocation of weak PRNG in mm/slab.c david.keisarschm
2022-12-18 18:18 ` [PATCH v3 2/3] Replace invocation of weak PRNG inside mm/slab_common.c david.keisarschm
2022-12-18 18:19 ` [PATCH v3 3/3] Replace invocation of weak PRNG in arch/x86/mm/kaslr.c david.keisarschm
2023-01-06 19:23   ` Kees Cook

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=cover.1671277662.git.david.keisarschm@mail.huji.ac.il \
    --to=david.keisarschm@mail.huji.ac.il \
    --cc=Jason@zx2c4.com \
    --cc=aksecurity@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=ilay.bahat1@gmail.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

all inboxes | Powered by JetHome®