From: WANG Rui <r@hev.cc>
To: Huacai Chen <chenhuacai@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
loongarch@lists.linux.dev, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, WANG Rui <r@hev.cc>
Subject: [RFC PATCH 0/3] LoongArch: Move KASLR to EFI stub to avoid initrd overlap
Date: Sun, 26 Apr 2026 20:02:28 +0800 [thread overview]
Message-ID: <20260426120231.532644-1-r@hev.cc> (raw)
This series addresses a potential overlap issue between the kernel
image and the initrd when KASLR is enabled.
In the normal boot flow, the bootloader is responsible for loading
both vmlinux and the initrd, and it can guarantee that the two do
not overlap in memory. However, this assumption only holds as long
as neither image changes its location afterwards.
The in-kernel KASLR implementation breaks that assumption. When the
initrd is placed close to the kernel image, randomizing the kernel
location at runtime may move it into the initrd region, leading to
memory corruption early during boot.
To fix this, this series moves the KASLR logic out of the kernel
proper and into the EFI stub. With this change, the final placement
of both the kernel image and the initrd is determined by the EFI
memory allocator. This ensures that the two allocations are
coordinated and cannot overlap.
Functionally, the kernel still supports KASLR as before, but the
randomization now happens before the kernel is entered, rather than
during early kernel relocation.
WANG Rui (3):
LoongArch: Allow rdtime_h and rdtime_l in 64-bit builds
efi/loongarch: Randomize kernel preferred address for KASLR
LoongArch: Remove KASLR handling from relocate_kernel()
arch/loongarch/include/asm/efi.h | 4 +-
arch/loongarch/include/asm/loongarch.h | 6 -
arch/loongarch/include/asm/setup.h | 2 +-
arch/loongarch/kernel/head.S | 12 --
arch/loongarch/kernel/relocate.c | 182 +----------------------
drivers/firmware/efi/libstub/loongarch.c | 15 ++
6 files changed, 24 insertions(+), 197 deletions(-)
--
2.54.0
next reply other threads:[~2026-04-26 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 12:02 WANG Rui [this message]
2026-04-26 12:02 ` [RFC PATCH 1/3] LoongArch: Allow rdtime_h and rdtime_l in 64-bit builds WANG Rui
2026-04-26 12:02 ` [RFC PATCH 2/3] efi/loongarch: Randomize kernel preferred address for KASLR WANG Rui
2026-04-27 5:07 ` Lisa Robinson
2026-04-27 7:49 ` hev
2026-04-26 12:02 ` [RFC PATCH 3/3] LoongArch: Remove KASLR handling from relocate_kernel WANG Rui
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=20260426120231.532644-1-r@hev.cc \
--to=r@hev.cc \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kernel@xen0n.name \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
/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