Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Will Deacon <will@kernel.org>, <linux-arm-kernel@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, Kees Cook <kees@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Yiqi Sun <sunyiqixm@gmail.com>
Subject: Re: [PATCH v3] arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
Date: Mon, 20 Jul 2026 20:02:56 +0800	[thread overview]
Message-ID: <63270b68-3f4b-40a1-b806-28639a7ca7fc@huawei.com> (raw)
In-Reply-To: <20260717182758.17111-1-will@kernel.org>



On 7/18/2026 2:27 AM, Will Deacon wrote:
> Commit e057b9477232 ("arm64: syscall: Ensure saved x0 is kept in-sync
> with tracer updates") attempted to resolve a long-standing issue with
> syscall entry tracing, where a tracer is able to manipulate the first
> syscall argument without being subjected to seccomp or audit checking.
> 
> Unfortunately, that fix was incomplete [1], as it failed to update
> 'orig_x0' between a tracer updating x0 during a seccomp ptrace exit
> (SECCOMP_RET_TRACE) and the seccomp filter being re-evaluated.
> 
> Rather than add hooks to the core seccomp code, instead move the
> synchronisation code into the ptrace GPR and syscall setting code so
> that 'orig_x0' is kept up to date with x0 whenever we're stopped on the
> syscall entry path.
> 
> Cc: Kees Cook <kees@kernel.org>
> Cc: Jinjie Ruan <ruanjinjie@huawei.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Link: https://sashiko.dev/#/patchset/20260716120640.6590-1-will@kernel.org [1]
> Reported-by: Yiqi Sun <sunyiqixm@gmail.com>
> Link: https://lore.kernel.org/all/20260529065444.1336608-1-sunyiqixm@gmail.com/
> Fixes: e057b9477232 ("arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates")
> Fixes: a5cd110cb836 ("arm64/ptrace: run seccomp after ptrace")
> Signed-off-by: Will Deacon <will@kernel.org>
> ---
>  arch/arm64/kernel/ptrace.c | 50 ++++++++++++++++++++++++++++++++++++++
>  1 file changed, 50 insertions(+)
> 
> v2: https://lore.kernel.org/r/20260716120640.6590-1-will@kernel.org
> 
> diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
> index 4d08598e2891..2b716fa11c02 100644
> --- a/arch/arm64/kernel/ptrace.c
> +++ b/arch/arm64/kernel/ptrace.c
> @@ -560,6 +560,42 @@ static int gpr_get(struct task_struct *target,
>  	return membuf_write(&to, uregs, sizeof(*uregs));
>  }
>  
> +static void update_syscall_orig_x0_after_ptrace(struct task_struct *target)
> +{
> +	struct pt_regs *regs = task_pt_regs(target);
> +	struct kernel_siginfo *info = target->last_siginfo;
> +
> +	/* We should only be called when target is in a ptrace stop */
> +	if (WARN_ON_ONCE(!info))
> +		return;
> +
> +	/*
> +	 * Skip the update for NO_SYSCALL (set either by the user or the
> +	 * tracer), as regs[0] holds the return value (see the comment in
> +	 * el0_svc_common()) and can be unwound using syscall_rollback().
> +	 */
> +	if (regs->syscallno == NO_SYSCALL)
> +		return;
> +
> +	/*
> +	 * For compat tasks, orig_r0 is provided directly through GPR index
> +	 * 17.
> +	 */
> +	if (is_compat_thread(task_thread_info(target)))
> +		return;
> +
> +	/*
> +	 * Don't update orig_x0 for a syscall-exit-stop, as x0 now contains the
> +	 * return value of the system call.
> +	 */
> +	if ((info->si_code & ~0x80) == SIGTRAP &&
> +	    target->ptrace_message == PTRACE_EVENTMSG_SYSCALL_EXIT) {
> +		return;
> +	}
> +
> +	regs->orig_x0 = regs->regs[0];
> +}
> +
>  static int gpr_set(struct task_struct *target, const struct user_regset *regset,
>  		   unsigned int pos, unsigned int count,
>  		   const void *kbuf, const void __user *ubuf)
> @@ -575,6 +611,14 @@ static int gpr_set(struct task_struct *target, const struct user_regset *regset,
>  		return -EINVAL;
>  
>  	task_pt_regs(target)->user_regs = newregs;
> +
> +	/*
> +	 * Keep orig_x0 authoritative so that seccomp (via
> +	 * syscall_get_arguments()), audit and the restart path all see the same
> +	 * first argument the syscall is dispatched with, even if it has been
> +	 * updated by a tracer.
> +	 */
> +	update_syscall_orig_x0_after_ptrace(target);

Tested-by: Jinjie Ruan <ruanjinjie@huawei.com>

>  	return 0;
>  }
>  
> @@ -753,6 +797,12 @@ static int system_call_set(struct task_struct *target,
>  		return ret;
>  
>  	task_pt_regs(target)->syscallno = syscallno;
> +
> +	/*
> +	 * Re-sync orig_x0 in case the syscall number has been changed
> +	 * from NO_SYSCALL.
> +	 */
> +	update_syscall_orig_x0_after_ptrace(target);
>  	return ret;
>  }
>  



      reply	other threads:[~2026-07-20 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17 18:27 [PATCH v3] arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry Will Deacon
2026-07-20 12:02 ` Jinjie Ruan [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=63270b68-3f4b-40a1-b806-28639a7ca7fc@huawei.com \
    --to=ruanjinjie@huawei.com \
    --cc=kees@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=sunyiqixm@gmail.com \
    --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