CVE-2026-90347arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
- 8.4HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
| NVDNVD · Received | 3.1 | High8.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.4.
Affected products
- affected a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 – < a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9
- affected a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 – < 332c9c1a148d0425326989c1187face8f6b2a60c
- affected a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 – < ce17c651a90e242ad48df0df89b1e4cebcda5e14
- affected a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 – < e9e2854fcff5733ffc607e8ecc87e0e591ab41fd
- affected a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 – < f433869f23841a50455c4087d85540d5b4d37cde
- affected a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615 – < 88b839ce497ccb1ff92f7ae742c78dd2937ba572
- affected 4.8
- unaffected < 4.8
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9 (opens in a new tab)
- https://git.kernel.org/stable/c/332c9c1a148d0425326989c1187face8f6b2a60c (opens in a new tab)
- https://git.kernel.org/stable/c/ce17c651a90e242ad48df0df89b1e4cebcda5e14 (opens in a new tab)
- https://git.kernel.org/stable/c/e9e2854fcff5733ffc607e8ecc87e0e591ab41fd (opens in a new tab)
- https://git.kernel.org/stable/c/f433869f23841a50455c4087d85540d5b4d37cde (opens in a new tab)
- https://git.kernel.org/stable/c/88b839ce497ccb1ff92f7ae742c78dd2937ba572 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82008 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90347)Record last updated .