From: "Seongsu Park" <sgsu.park@samsung.com>
To: "'Yeo Reum Yun'" <YeoReum.Yun@arm.com>
Cc: "'Catalin Marinas'" <Catalin.Marinas@arm.com>, <will@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] arm64: Fix PIE_E1 mapping for _PAGE_READONLY_EXEC
Date: Sun, 28 Dec 2025 02:38:59 +0900 [thread overview]
Message-ID: <000001dc7757$af3294a0$0d97bde0$@samsung.com> (raw)
In-Reply-To: <GV1PR08MB105210D9BD328C2446CA8C551FBB1A@GV1PR08MB10521.eurprd08.prod.outlook.com>
Hi Yeoreum,
> NIT: This looks like it allows executing user code from the kernel.
> Why is this necessary?
Good Catch. You're absolutely right.
I misunderstood how PIE separates EL0/EL1 permissions.
The kernel should only have read access to the executing user code pages.
The original PIE_EL1 mapping to PIE_R is correct.
My patch would be a security regression. Please disregard.
Thanks for the careful review,
Seongsu Park.
prev parent reply other threads:[~2025-12-27 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251227070633epcas1p3a8f7c19c9f5114a46765073fa16ba449@epcas1p3.samsung.com>
2025-12-27 7:06 ` Seongsu Park
2025-12-27 15:46 ` Yeo Reum Yun
2025-12-27 17:38 ` Seongsu Park [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='000001dc7757$af3294a0$0d97bde0$@samsung.com' \
--to=sgsu.park@samsung.com \
--cc=Catalin.Marinas@arm.com \
--cc=YeoReum.Yun@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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®