[PATCH v3 0/2] ptrace: reject out of range error values in PTRACE_SET_SYSCALL_INFO
From: Renzo Davoli
Date: Sun Nov 15 2026 - 10:27:31 EST
With is_error set, PTRACE_SET_SYSCALL_INFO passes info.exit.rval to
syscall_set_return_value() as an "int" error without checking it: a
positive value, or on 64-bit one outside the "int" range, turns the
error into a success or is truncated.
Patch 1 rejects with -ERANGE any error value outside [-MAX_ERRNO, -1].
Patch 2 adds a test case for this to the set_syscall_info selftest.
This series is independent of the PTRACE_SET_SYSCALL_INFO seccomp skip
and SET_IP series: they apply on top of each other in either order.
Changes in v3:
* added Reviewed-by of Dmitry V. Levin and Bradley Morgan to patch 1
* new patch 2: selftest, as suggested by Dmitry V. Levin
Changes in v2:
* shorter commit message and comment, dropped Assisted-by
(Bradley Morgan)
v2: https://lore.kernel.org/lkml/20261115082540.385386-1-renzo@xxxxxxxxxxx/
v1: https://lore.kernel.org/lkml/20261114184842.373304-1-renzo@xxxxxxxxxxx/
Renzo Davoli (2):
ptrace: reject out of range error values in PTRACE_SET_SYSCALL_INFO
selftests/ptrace: check that PTRACE_SET_SYSCALL_INFO rejects invalid
error values
kernel/ptrace.c | 4 ++
.../selftests/ptrace/set_syscall_info.c | 51 +++++++++++++++++++
2 files changed, 55 insertions(+)
base-commit: 7e1392a42ea288d70a266f6553fe06f57f8647ea
--
2.47.3