CVE-2026-90347

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-82008 (ENISA EUVD) · GHSA-rg84-frxc-rfcx (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 17, 2026

Last Modified

October 30, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
Patch available.
Web page

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
Web page

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

Patch Availability(5)

These rows come from Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (375 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (182 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 8× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 233 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-90347?
CVE-2026-90347 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-90347 published?
The CVE record for CVE-2026-90347 was published on September 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
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 (5th 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?
A fix for CVE-2026-90347 is available: update to the fixed version the vendor names in its advisory. 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.