From: Nathan Lynch <nathanl@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: jmorris@namei.org, mpe@ellerman.id.au, paul@paul-moore.com,
serge@hallyn.com, ajd@linux.ibm.com, gcwilson@linux.ibm.com,
nayna@linux.ibm.com
Subject: [PATCH 0/2] powerpc/pseries: restrict error injection and DT changes when locked down
Date: Thu, 22 Sep 2022 14:38:15 -0500 [thread overview]
Message-ID: <20220922193817.106041-1-nathanl@linux.ibm.com> (raw)
Add two new lockdown reasons for use in powerpc's pseries platform
code.
The pseries platform allows hardware-level error injection via certain
calls to the RTAS (Run Time Abstraction Services) firmware. ACPI-based
error injection is already restricted in lockdown; this facility
should be restricted for the same reasons.
pseries also allows nearly arbitrary device tree changes via
/proc/powerpc/ofdt. Just as overriding ACPI tables is not allowed
while locked down, so should this facility be restricted.
Nathan Lynch (2):
powerpc/pseries: block untrusted device tree changes when locked down
powerpc/rtas: block error injection when locked down
arch/powerpc/kernel/rtas.c | 25 ++++++++++++++++++++++-
arch/powerpc/platforms/pseries/reconfig.c | 5 +++++
include/linux/security.h | 2 ++
security/security.c | 2 ++
4 files changed, 33 insertions(+), 1 deletion(-)
--
2.37.3
next reply other threads:[~2022-09-22 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:38 Nathan Lynch [this message]
2022-09-22 19:38 ` [PATCH 1/2] powerpc/pseries: block untrusted device tree changes when locked down Nathan Lynch
2022-09-23 1:18 ` Paul Moore
2022-09-23 7:03 ` Michael Ellerman
2022-09-23 15:58 ` Nathan Lynch
2022-09-22 19:38 ` [PATCH 2/2] powerpc/rtas: block error injection " Nathan Lynch
2022-09-23 1:28 ` Paul Moore
2022-09-23 7:12 ` Michael Ellerman
2022-09-23 15:39 ` Nathan Lynch
2022-09-23 17:42 ` Paul Moore
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=20220922193817.106041-1-nathanl@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=gcwilson@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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;
as well as URLs for NNTP newsgroup(s).