From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Feng Liu <Feng.Liu3@windriver.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y/5.15.y] ELF: fix kernel.randomize_va_space double read
Date: Mon, 12 May 2025 14:04:55 -0400 [thread overview]
Message-ID: <20250511221746-17a0e7ea300c9d83@stable.kernel.org> (raw)
In-Reply-To: <20250509061415.435740-1-Feng.Liu3@windriver.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 2a97388a807b6ab5538aa8f8537b2463c6988bd2
WARNING: Author mismatch between patch and upstream commit:
Backport author: Feng Liu<Feng.Liu3@windriver.com>
Commit author: Alexey Dobriyan<adobriyan@gmail.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 53f17409abf6)
6.1.y | Present (different SHA1: 1f81d51141a2)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 2a97388a807b6 ! 1: 795c22f390cda ELF: fix kernel.randomize_va_space double read
@@ Metadata
## Commit message ##
ELF: fix kernel.randomize_va_space double read
+ [ Upstream commit 2a97388a807b6ab5538aa8f8537b2463c6988bd2 ]
+
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.
@@ Commit message
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Link: https://lore.kernel.org/r/3329905c-7eb8-400a-8f0a-d87cff979b5b@p183
Signed-off-by: Kees Cook <kees@kernel.org>
+ Signed-off-by: Feng Liu <Feng.Liu3@windriver.com>
+ Signed-off-by: He Zhe <Zhe.He@windriver.com>
## fs/binfmt_elf.c ##
@@ fs/binfmt_elf.c: static int load_elf_binary(struct linux_binprm *bprm)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-05-12 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 6:14 [PATCH 5.10.y/5.15.y] ELF: fix kernel.randomize_va_space double read Feng Liu
2025-05-12 18:04 ` Sasha Levin [this message]
2025-05-20 11:25 ` Greg KH
2025-05-22 7:40 ` He Zhe
2025-05-22 7:44 ` He Zhe
2025-05-22 8:36 ` Greg KH
2025-05-22 9:26 ` He Zhe
2025-05-22 9:40 ` Greg KH
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=20250511221746-17a0e7ea300c9d83@stable.kernel.org \
--to=sashal@kernel.org \
--cc=Feng.Liu3@windriver.com \
--cc=stable@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