CVE-2026-90347

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.4
EG Score
8.4HIGHhigh confidence
EG Risk
42
EG Risk 42/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88b839ce497ccb1ff92f7ae742c78dd2937ba572
generic

arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f433869f23841a50455c4087d85540d5b4d37cde

Vendor Advisories for CVE-2026-90347(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 41× in last 7d / 106× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 106 total refreshes for this CVE.

  1. 2026-10-05 03:07 UTCEG score recompute
  2. 2026-10-05 03:07 UTCVendor advisory
  3. 2026-10-05 03:07 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 15:44 UTCVendor advisory
  6. 2026-10-04 15:44 UTCGHSA enrichment
  7. 2026-10-04 04:38 UTCVendor advisory
  8. 2026-10-04 04:38 UTCGHSA enrichment
  9. 2026-10-03 17:32 UTCVendor advisory
  10. 2026-10-03 17:32 UTCGHSA enrichment
  11. 2026-10-03 06:27 UTCVendor advisory
  12. 2026-10-03 06:27 UTCGHSA enrichment
  13. 2026-10-02 19:21 UTCEG score recompute
  14. 2026-10-02 19:21 UTCVendor advisory
  15. 2026-10-02 19:21 UTCGHSA enrichment
  16. 2026-10-02 08:14 UTCVendor advisory
  17. 2026-10-02 08:14 UTCGHSA enrichment
  18. 2026-10-01 21:06 UTCEG score recompute
  19. 2026-10-01 21:06 UTCVendor advisory
  20. 2026-10-01 21:06 UTCGHSA enrichment
  21. 2026-10-01 19:51 UTCEPSS rescore
  22. 2026-10-01 10:00 UTCVendor advisory
  23. 2026-10-01 10:00 UTCGHSA enrichment
  24. 2026-09-30 22:54 UTCEG score recompute
  25. 2026-09-30 22:54 UTCVendor advisory
Show 75 more
  1. 2026-09-30 22:54 UTCGHSA enrichment
  2. 2026-09-30 15:04 UTCEPSS rescore
  3. 2026-09-30 11:49 UTCVendor advisory
  4. 2026-09-30 11:49 UTCGHSA enrichment
  5. 2026-09-30 00:43 UTCEG score recompute
  6. 2026-09-30 00:43 UTCVendor advisory
  7. 2026-09-30 00:43 UTCGHSA enrichment
  8. 2026-09-29 09:46 UTCVendor advisory
  9. 2026-09-29 09:46 UTCGHSA enrichment
  10. 2026-09-28 22:41 UTCEG score recompute
  11. 2026-09-28 22:41 UTCVendor advisory
  12. 2026-09-28 22:40 UTCGHSA enrichment
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 11:34 UTCVendor advisory
  16. 2026-09-28 11:34 UTCGHSA enrichment
  17. 2026-09-28 00:28 UTCEG score recompute
  18. 2026-09-28 00:28 UTCVendor advisory
  19. 2026-09-28 00:28 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 13:22 UTCVendor advisory
  22. 2026-09-27 13:22 UTCGHSA enrichment
  23. 2026-09-27 02:16 UTCEG score recompute
  24. 2026-09-27 02:16 UTCVendor advisory
  25. 2026-09-27 02:16 UTCGHSA enrichment
  26. 2026-09-26 15:59 UTCEPSS rescore
  27. 2026-09-26 15:09 UTCVendor advisory
  28. 2026-09-26 15:09 UTCGHSA enrichment
  29. 2026-09-26 04:03 UTCEG score recompute
  30. 2026-09-26 04:03 UTCVendor advisory
  31. 2026-09-26 04:03 UTCGHSA enrichment
  32. 2026-09-25 16:56 UTCVendor advisory
  33. 2026-09-25 16:56 UTCGHSA enrichment
  34. 2026-09-25 05:50 UTCVendor advisory
  35. 2026-09-25 05:50 UTCGHSA enrichment
  36. 2026-09-24 18:44 UTCEG score recompute
  37. 2026-09-24 18:44 UTCVendor advisory
  38. 2026-09-24 18:44 UTCGHSA enrichment
  39. 2026-09-24 14:04 UTCEPSS rescore
  40. 2026-09-24 07:39 UTCVendor advisory
  41. 2026-09-24 07:39 UTCGHSA enrichment
  42. 2026-09-23 20:32 UTCEG score recompute
  43. 2026-09-23 20:32 UTCVendor advisory
  44. 2026-09-23 20:32 UTCGHSA enrichment
  45. 2026-09-23 17:54 UTCEPSS rescore
  46. 2026-09-23 09:27 UTCVendor advisory
  47. 2026-09-23 09:27 UTCGHSA enrichment
  48. 2026-09-22 22:21 UTCEG score recompute
  49. 2026-09-22 22:21 UTCVendor advisory
  50. 2026-09-22 22:21 UTCGHSA enrichment
  51. 2026-09-22 16:01 UTCEPSS rescore
  52. 2026-09-22 11:15 UTCVendor advisory
  53. 2026-09-22 11:15 UTCGHSA enrichment
  54. 2026-09-22 00:09 UTCEG score recompute
  55. 2026-09-22 00:09 UTCVendor advisory
  56. 2026-09-22 00:09 UTCGHSA enrichment
  57. 2026-09-21 21:09 UTCEPSS rescore
  58. 2026-09-21 13:04 UTCVendor advisory
  59. 2026-09-21 13:04 UTCGHSA enrichment
  60. 2026-09-21 01:58 UTCEG score recompute
  61. 2026-09-21 01:58 UTCVendor advisory
  62. 2026-09-21 01:58 UTCGHSA enrichment
  63. 2026-09-20 20:16 UTCEPSS rescore
  64. 2026-09-20 14:52 UTCVendor advisory
  65. 2026-09-20 14:52 UTCGHSA enrichment
  66. 2026-09-20 03:47 UTCVendor advisory
  67. 2026-09-20 03:47 UTCGHSA enrichment
  68. 2026-09-19 16:41 UTCEG score recompute
  69. 2026-09-19 16:41 UTCVendor advisory
  70. 2026-09-19 16:41 UTCGHSA enrichment
  71. 2026-09-19 05:35 UTCEG score recompute
  72. 2026-09-19 05:35 UTCGHSA enrichment
  73. 2026-09-18 19:28 UTCEPSS rescore
  74. 2026-09-18 18:30 UTCEG score recompute
  75. 2026-09-18 18:30 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-90347?
CVE-2026-90347 is a high vulnerability published on September 17, 2026. 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…
When was CVE-2026-90347 disclosed?
CVE-2026-90347 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90347 actively exploited?
CVE-2026-90347 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90347?
CVE-2026-90347 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90347?
No fix for CVE-2026-90347 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90347 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90347

Explore →

Is Your Infrastructure Affected by CVE-2026-90347?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs