+ kernel-fork-validate-exit_signal-in-kernel_clone.patch added to mm-nonmm-unstable branch
Subsystems (3)
The patch titled
Subject: kernel/fork: validate exit_signal in kernel_clone()
has been added to the -mm mm-nonmm-unstable branch. Its filename is
kernel-fork-validate-exit_signal-in-kernel_clone.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/kernel-fork-validate-exit_signal-in-kernel_clone.patch
This patch will later appear in the mm-nonmm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Deepanshu Kartikey <[email protected]>
Subject: kernel/fork: validate exit_signal in kernel_clone()
Date: Mon, 16 Mar 2026 20:49:56 +0530
When a child process exits, it sends exit_signal to its parent via do_notify_parent(). The clone() syscall constructs exit_signal as:
(lower_32_bits(clone_flags) & CSIGNAL)
CSIGNAL is 0xff, so values in the range 65-255 are possible. However, valid_signal() only accepts signals up to _NSIG (64 on x86_64). A non-zero non-valid exit_signal acts the same as exit_signal == 0: the parent process is not signaled when the child terminates.
The syzkaller reproducer triggers this by calling clone() with flags=0x80, resulting in exit_signal = (0x80 & CSIGNAL) = 128, which exceeds _NSIG and is not a valid signal.
The v1 of this patch added the check only in the clone() syscall handler, which is incomplete. kernel_clone() has other callers such as sys_ia32_clone() which would remain unprotected. Move the check to kernel_clone() to cover all callers.
Since the valid_signal() check is now in kernel_clone() and covers all callers including clone3(), the same check in copy_clone_args_from_user() becomes redundant and is removed. The higher 32bits check for clone3() is kept as it is clone3() specific.
Note that this is a user-visible change: previously, passing an invalid exit_signal to clone() was silently accepted. The man page for clone() does not document any defined behavior for invalid exit_signal values, so rejecting them with -EINVAL is the correct behavior. It is unlikely that any sane application relies on passing an invalid exit_signal.
---
kernel/fork.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
kernel/fork.c renamed from kernel/fork.c~kernel-fork-validate-exit_signal-in-kernel_clone +5 -4
@@ -2642,6 +2642,9 @@ pid_t kernel_clone(struct kernel_clone_a (args->pidfd == args->parent_tid))return -EINVAL ; +if (!valid_signal (args->exit_signal)) +return -EINVAL ; +/* * Determine whether and which event to report to ptracer. When * called from kernel_thread or CLONE_UNTRACED is explicitly
@@ -2840,11 +2843,9 @@ static noinline int copy_clone_args_fromreturn -EINVAL ;/* -* Verify that higher 32bits of exit_signal are unset and that -* it is a valid signal +* Verify that higher 32bits of exit_signal are unset */ -if (unlikely ((args.exit_signal & ~((u64 )CSIGNAL )) || - !valid_signal (args.exit_signal))) +if (unlikely (args.exit_signal & ~((u64 )CSIGNAL )))return -EINVAL ; if ((args.flags & CLONE_INTO_CGROUP) &&
_
Patches currently in -mm which might be from [email protected] are
kernel-fork-validate-exit_signal-in-kernel_clone.patch
PATCH 1/1 kernel-fork-validate-exit_signal-in-kernel_clone-fix
Andrew, can you fold this trivial fixup into
kernel-fork-validate-exit_signal-in-kernel_clone.patch
? the comment above kernel_clone() shoule be updated.
--- kernel/fork.c | 2 -- 1 file changed, 2 deletions(-)
kernel/fork.c +0 -2
@@ -2614,8 +2614,6 @@ struct task_struct *create_io_thread(int (*fn)(void *), void *arg, int node)* * It copies the process, and if successful kick-starts * it and waits for it to finish using the VM if required. -* -* args->exit_signal is expected to be checked for sanity by the caller. */ pid_t kernel_clone (struct kernel_clone_args *args) {
Signature · 1 line
2.52.0