CVE-2026-90347

arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry

State
Published
Severity
8.4 High
Published
Sep 17, 2026
Updated
Oct 30, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.18.4 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to before a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9Affected
  • a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to before 332c9c1a148d0425326989c1187face8f6b2a60cAffected
  • a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to before ce17c651a90e242ad48df0df89b1e4cebcda5e14Affected
  • a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to before e9e2854fcff5733ffc607e8ecc87e0e591ab41fdAffected
  • a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to before f433869f23841a50455c4087d85540d5b4d37cdeAffected
  • a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 to before 88b839ce497ccb1ff92f7ae742c78dd2937ba572Affected
LinuxLinux
  • 4.8Affected
  • before 4.8Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.114 through 6.12.*Not affected
  • 6.18.57 through 6.18.*Not affected
  • 7.2.6 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.