From: Kees Cook <kees@kernel.org>
To: Eric Biederman <ebiederm@xmission.com>,
Alexey Dobriyan <adobriyan@gmail.com>
Cc: Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] ELF: fix kernel.randomize_va_space double read
Date: Fri, 21 Jun 2024 12:40:39 -0700 [thread overview]
Message-ID: <171899883660.3914852.8274555416549796593.b4-ty@kernel.org> (raw)
In-Reply-To: <3329905c-7eb8-400a-8f0a-d87cff979b5b@p183>
On Fri, 21 Jun 2024 21:54:50 +0300, Alexey Dobriyan wrote:
> ELF loader uses "randomize_va_space" twice. It is sysctl and can change
> at any moment, so 2 loads could see 2 different values in theory with
> unpredictable consequences.
>
> Issue exactly one load for consistent value across one exec.
>
>
> [...]
Applied to for-next/execve, thanks!
[1/1] ELF: fix kernel.randomize_va_space double read
https://git.kernel.org/kees/c/2a97388a807b
Take care,
--
Kees Cook
prev parent reply other threads:[~2024-06-21 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 18:54 Alexey Dobriyan
2024-06-21 19:40 ` Kees Cook [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=171899883660.3914852.8274555416549796593.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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