Go to homepageCyberStrike

Menu

Star on GitHub · 3.4k
Sign inDownload

CVE-2026-90347

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…

Published Sep 17, 2026EPSS 0.17%

Overview

CVE-2026-90347 is a high-severity vulnerability. It was published on September 17, 2026 and has a CVSS 3.1 base score of 8.4 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/332c9c1a148d0425326989c1187face8f6b2a60cRefgit.kernel.org/stable/c/88b839ce497ccb1ff92f7ae742c78dd2937ba572Refgit.kernel.org/stable/c/a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9Refgit.kernel.org/stable/c/ce17c651a90e242ad48df0df89b1e4cebcda5e14Refgit.kernel.org/stable/c/e9e2854fcff5733ffc607e8ecc87e0e591ab41fdRefgit.kernel.org/stable/c/f433869f23841a50455c4087d85540d5b4d37cde

How CyberStrike helps

Frequently asked questions

What is CVE-2026-90347?

CVE-2026-90347 is a high-severity vulnerability. It was published on September 17, 2026 and has a CVSS 3.1 base score of 8.4 (HIGH).

How severe is CVE-2026-90347?

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-90347?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-90347?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-90347 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999
Watch the demo →