From: Bill Roberts <bill.roberts@arm.com>
To: rick.p.edgecombe@intel.com, Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: Bill Roberts <bill.roberts@arm.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] arch/x86: do not allow unlock to set bits
Date: Mon, 15 Jun 2026 14:51:54 -0500 [thread overview]
Message-ID: <20260615195156.257950-1-bill.roberts@arm.com> (raw)
Currently, the code for handling arch_prctl for shadow stack operations
is written to exit early on all operations but enable. However, the
check for ARCH_SHSTK_UNLOCK is gated on a check for task != current,
which means that if current == task, ARCH_SHSTK_UNLOCK can be used to
set feature bits by virtue of skipping that check.
This seems not as intended, and the check should first check that the
operation is ARCH_SHSTK_UNLOCK and then check the task status to
determine the error code.
Signed-off-by: Bill Roberts <bill.roberts@arm.com>
---
arch/x86/kernel/shstk.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kernel/shstk.c b/arch/x86/kernel/shstk.c
index 0ca64900192f..664167f94acd 100644
--- a/arch/x86/kernel/shstk.c
+++ b/arch/x86/kernel/shstk.c
@@ -583,12 +583,13 @@ long shstk_prctl(struct task_struct *task, int option, unsigned long arg2)
}
/* Only allow via ptrace */
- if (task != current) {
- if (option == ARCH_SHSTK_UNLOCK && IS_ENABLED(CONFIG_CHECKPOINT_RESTORE)) {
- task->thread.features_locked &= ~features;
- return 0;
- }
- return -EINVAL;
+ if (option == ARCH_SHSTK_UNLOCK) {
+ if (task == current)
+ return -EPERM;
+ if (!IS_ENABLED(CONFIG_CHECKPOINT_RESTORE))
+ return -EINVAL;
+ task->thread.features_locked &= ~features;
+ return 0;
}
/* Do not allow to change locked features */
--
2.54.0
next reply other threads:[~2026-06-15 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 19:51 Bill Roberts [this message]
2026-06-15 19:51 ` [PATCH 2/2] selftest/x86: test ARCH_SHSTK_UNLOCK Bill Roberts
2026-06-29 21:46 ` Edgecombe, Rick P
2026-06-29 17:09 ` Bill Roberts
2026-06-30 17:02 ` Edgecombe, Rick P
2026-06-29 21:57 ` Edgecombe, Rick P
2026-06-29 17:13 ` Bill Roberts
2026-06-29 21:44 ` [PATCH 1/2] arch/x86: do not allow unlock to set bits Edgecombe, Rick P
2026-06-29 17:05 ` Bill Roberts
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=20260615195156.257950-1-bill.roberts@arm.com \
--to=bill.roberts@arm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@kernel.org \
--cc=x86@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®