Azure RTOS USBX Remote Code Execution Vulnerability

published 2023-12-05 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-52740

cvss: 6.7; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS ThreadX. An attacker can cause remote code execution due to expired pointer dereference vulnerabilities in Azure RTOS USBX. The affected components include components in host class, related to CDC ACM in RTOS v6.2.1 and below. The fixes have been included in USBX release 6.3.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Patch / fix

fixed in 1

eclipse threadx_usbx 6.3.0

Exploit prediction

0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.7	CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

azure-rtos usbx

Classification

Weakness

CWE-825 Expired Pointer Dereference
CWE-754 Improper Check for Unusual or Exceptional Conditions

References

github.com /azure-rtos/usbx/security/advisories/GHSA-h733-98hq-f884
third-party-advisory

Sources

CVE List CVE-2023-48696
NVD CVE-2023-48696

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary