CVE-2026-90347
In the Linux kernel, the following vulnerability has been resolved: arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry 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.
- CVSS 3.1
- 8.4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N - EPSS
- 0.2% chance of exploitation in the next 30 days; higher than 6% of CVEs (scores of 2026-10-25)
- Published
- Modified
- Record from
- the NVD, synced
References
- https://git.kernel.org/stable/c/332c9c1a148d0425326989c1187face8f6b2a60c
- https://git.kernel.org/stable/c/88b839ce497ccb1ff92f7ae742c78dd2937ba572
- https://git.kernel.org/stable/c/ce17c651a90e242ad48df0df89b1e4cebcda5e14
- https://git.kernel.org/stable/c/e9e2854fcff5733ffc607e8ecc87e0e591ab41fd
- https://git.kernel.org/stable/c/f433869f23841a50455c4087d85540d5b4d37cde