From: Gregory Price <gourry@gourry.net>
To: linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, kernel-team@meta.com, corbet@lwn.net,
skhan@linuxfoundation.org, tglx@kernel.org, peterz@infradead.org,
luto@kernel.org, akpm@linux-foundation.org,
feng.tang@linux.alibaba.com, pmladek@suse.com,
mhiramat@kernel.org, marc.herbert@linux.intel.com,
joel.granados@kernel.org, gourry@gourry.net,
lirongqing@baidu.com, kees@kernel.org, nathan@kernel.org,
linusw@kernel.org, arnd@arndb.de, deller@gmx.de,
jpoimboe@kernel.org, ruanjinjie@huawei.com,
lukas.bulwahn@redhat.com, ryan.roberts@arm.com, ojeda@kernel.org
Subject: [PATCH 2/2] kernel/entry: add kernel.syscall_user_dispatch sysctl
Date: Sat, 27 Jun 2026 16:55:51 -0400 [thread overview]
Message-ID: <20260627205551.769684-2-gourry@gourry.net> (raw)
In-Reply-To: <20260627205551.769684-1-gourry@gourry.net>
Add a matching sysctl to go with CONFIG_SYSCALL_USER_DISPATCH.
kernel.syscall_user_dispatch (default 1) controls whether userspace
may arm SUD (both via prctl and ptrace).
Disarming is always permitted - same semantics as comparable knobs
Signed-off-by: Gregory Price <gourry@gourry.net>
---
Documentation/admin-guide/sysctl/kernel.rst | 17 +++++++++++++
kernel/entry/syscall_user_dispatch.c | 28 +++++++++++++++++++++
2 files changed, 45 insertions(+)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index c6994e55d141..4c90caaf1e21 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -1402,6 +1402,23 @@ Note that if you change this from 0 to 1, already created segments
without users and with a dead originative process will be destroyed.
+syscall_user_dispatch
+=====================
+
+Controls whether userspace may arm Syscall User Dispatch (SUD) via
+``prctl(PR_SET_SYSCALL_USER_DISPATCH, ...)`` or the
+``PTRACE_SET_SYSCALL_USER_DISPATCH_CONFIG`` ptrace request:
+
+ == ===================================================================
+ 0 Arming SUD is denied with ``-EPERM``. Tasks that already armed it
+ keep it, and disabling SUD (``PR_SYS_DISPATCH_OFF``) is always
+ permitted.
+ 1 (default) Arming SUD is permitted.
+ == ===================================================================
+
+Only present when the kernel is built with ``CONFIG_SYSCALL_USER_DISPATCH``.
+
+
sysctl_writes_strict
====================
diff --git a/kernel/entry/syscall_user_dispatch.c b/kernel/entry/syscall_user_dispatch.c
index d89dffcc2d64..1c39ccd733f5 100644
--- a/kernel/entry/syscall_user_dispatch.c
+++ b/kernel/entry/syscall_user_dispatch.c
@@ -11,12 +11,15 @@
#include <linux/uaccess.h>
#include <linux/signal.h>
#include <linux/elf.h>
+#include <linux/sysctl.h>
#include <linux/sched/signal.h>
#include <linux/sched/task_stack.h>
#include <asm/syscall.h>
+static int syscall_user_dispatch_allowed __read_mostly = 1;
+
static void trigger_sigsys(struct pt_regs *regs)
{
struct kernel_siginfo info;
@@ -102,6 +105,10 @@ static int task_set_syscall_user_dispatch(struct task_struct *task, unsigned lon
return -EINVAL;
}
+ /* Arming can be denied at runtime via sysctl, disarming is allowed */
+ if (mode != PR_SYS_DISPATCH_OFF && !syscall_user_dispatch_allowed)
+ return -EPERM;
+
/*
* access_ok() will clear memory tags for tagged addresses
* if current has memory tagging enabled.
@@ -172,3 +179,24 @@ int syscall_user_dispatch_set_config(struct task_struct *task, unsigned long siz
return task_set_syscall_user_dispatch(task, cfg.mode, cfg.offset, cfg.len,
(char __user *)(uintptr_t)cfg.selector);
}
+
+#ifdef CONFIG_SYSCTL
+static const struct ctl_table syscall_user_dispatch_sysctls[] = {
+ {
+ .procname = "syscall_user_dispatch",
+ .data = &syscall_user_dispatch_allowed,
+ .maxlen = sizeof(syscall_user_dispatch_allowed),
+ .mode = 0644,
+ .proc_handler = proc_dointvec_minmax,
+ .extra1 = SYSCTL_ZERO,
+ .extra2 = SYSCTL_ONE,
+ },
+};
+
+static int __init syscall_user_dispatch_sysctl_init(void)
+{
+ register_sysctl_init("kernel", syscall_user_dispatch_sysctls);
+ return 0;
+}
+late_initcall(syscall_user_dispatch_sysctl_init);
+#endif /* CONFIG_SYSCTL */
--
2.54.0
next prev parent reply other threads:[~2026-06-27 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 20:55 [PATCH 1/2] kernel/entry: add CONFIG_SYSCALL_USER_DISPATCH to compile SUD out Gregory Price
2026-06-27 20:55 ` Gregory Price [this message]
2026-07-03 15:46 ` [PATCH 2/2] kernel/entry: add kernel.syscall_user_dispatch sysctl Thomas Gleixner
2026-07-03 17:26 ` Gregory Price
2026-07-03 19:06 ` Thomas Gleixner
2026-07-03 15:39 ` [PATCH 1/2] kernel/entry: add CONFIG_SYSCALL_USER_DISPATCH to compile SUD out Thomas Gleixner
2026-07-03 17:22 ` Gregory Price
2026-07-03 19:05 ` Thomas Gleixner
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=20260627205551.769684-2-gourry@gourry.net \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=deller@gmx.de \
--cc=feng.tang@linux.alibaba.com \
--cc=joel.granados@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=kernel-team@meta.com \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=lukas.bulwahn@redhat.com \
--cc=luto@kernel.org \
--cc=marc.herbert@linux.intel.com \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=tglx@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