CVE-2026-90347
Last modified
CVE-2026-90347 is a high-severity vulnerability rated 8.4/10 on the CVSS scale. 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..
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, < f433869f23841a50455c4087d85540d5b4d37cde; >= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, < 88b839ce497ccb1ff92f7ae742c78dd2937ba572 |
| Linux | Linux | 4.8 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90347?
How severe is CVE-2026-90347?
How do I fix CVE-2026-90347?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90341In the Linux kernel, the following vulnerability has been re…7.7
- CVE-2026-90342In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90343In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90344In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90345In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90346In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90348In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90349In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9035IBM Aspera High-Speed Transfer Endpoint 3.7.4 through 4.4.7 …6.5
- CVE-2026-90350In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90351In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90352In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-90347?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
