Azure RTOS USBX is a high-performance USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS ThreadX. The case is, in _ux_host_class_pima_read, there is data length from device response, returned in the very first packet, and read by L165 code, as header_length. Then in L178 code, there is a “if” branch, which check the expression of “(header_length - UX_HOST_CLASS_PIMA_DATA_HEADER_SIZE) > data_length” where if header_length is smaller than UX_HOST_CLASS_PIMA_DATA_HEADER_SIZE, calculation could overflow and then L182 code the calculation of data_length is also overflow, this way the later while loop start from L192 can move data_pointer to unexpected address and cause write buffer overflow. The fix has been included in USBX release 6.1.12. The following can be used as a workaround: Add check of header_length: 1. It must be greater than UX_HOST_CLASS_PIMA_DATA_HEADER_SIZE. 1. It should be greater or equal to the current returned data length (transfer_request -> ux_transfer_request_actual_length).
CVE-2022-39293
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.8% (57th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.6
- EG Score
- 8.6HIGHmedium confidence
- EG Risk
- 54EG Risk 54/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)Severity86% × 45%Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.8% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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 at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.8%
- EPSS %ILE
- 57th
- 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.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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
October 13, 2022
Last Modified
October 27, 2025
Advisory Details (2)
Auto-updated Sep 2, 2026Azure RTOS USBX Host PIMA read integer underflow with buffer overflow · Advisory · eclipse-threadx/usbx · GitHub
https://github.com/azure-rtos/usbx/security/advisories/GHSA-gg76-h537-xq48Azure RTOS 6.1.12
Patch available: azure-rtos/usbx v6.1.12_rel
https://github.com/azure-rtos/usbx/releases/tag/v6.1.12_relWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 34× 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 it from the CNA feed. 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). Most recent first.
Showing the most recent 93 of 199 refreshes 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-21 06:23 UTCEG score recompute
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-18 08:28 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-15 14:54 UTCOSV refresh
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-12 18:48 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-11 23:12 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 68 moreShow fewer
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-30 16:03 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-24 07:56 UTCOSV refresh
- 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-17 19:24 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-05 01:44 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-18 12:31 UTCOSV refresh
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-10 14:08 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-03 07:57 UTCOSV refresh
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-07-23 02:13 UTCEG score recompute
- 2026-07-22 23:00 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2022-39293?
When was the CVE record for CVE-2022-39293 published?
Is CVE-2022-39293 actively exploited?
What is the CVSS score of CVE-2022-39293?
How do I remediate CVE-2022-39293?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-39293
Is Your Infrastructure Affected by CVE-2022-39293?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.