CVE-2026-90347

Source
https://cve.org/CVERecord?id=CVE-2026-90347
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90347.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-90347
Downstream
Published
2026-09-17T16:08:56Z
Modified
2026-09-18T03:48:37Z
Summary
arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90347.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615
Fixed
f433869f23841a50455c4087d85540d5b4d37cde
Fixed
88b839ce497ccb1ff92f7ae742c78dd2937ba572

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90347.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
4.8.0
Fixed
7.2.6

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90347.json"