Vulnerability Description
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 Score
HIGH
References
- https://git.kernel.org/stable/c/88b839ce497ccb1ff92f7ae742c78dd2937ba572
- https://git.kernel.org/stable/c/f433869f23841a50455c4087d85540d5b4d37cde
FAQ
What is CVE-2026-90347?
CVE-2026-90347 is a vulnerability with a CVSS score of 8.4 (HIGH). 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-sy...
How severe is CVE-2026-90347?
CVE-2026-90347 has been rated HIGH with a CVSS base score of 8.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-90347?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.