arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
CVE-2026-90347 · published 17 Sept 2026
How serious is it
- Severity: high, CVSS score 8.4 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-90347?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to < 332c9c1a148d0425326989c1187face8f6b2a60c, a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to < ce17c651a90e242ad48df0df89b1e4cebcda5e14, a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to < e9e2854fcff5733ffc607e8ecc87e0e591ab41fd, a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to < f433869f23841a50455c4087d85540d5b4d37cde
- Linux Linux: 4.8
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/332c9c1a148d0425326989c1187face8f6b2a60c
- git.kernel.org/stable/c/ce17c651a90e242ad48df0df89b1e4cebcda5e14
- git.kernel.org/stable/c/e9e2854fcff5733ffc607e8ecc87e0e591ab41fd
- git.kernel.org/stable/c/f433869f23841a50455c4087d85540d5b4d37cde
- git.kernel.org/stable/c/88b839ce497ccb1ff92f7ae742c78dd2937ba572
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON