Skip to main content

ThreadX USBX CVE-2025-55098

LOW
Out-of-bounds Read (CWE-125)
2025-10-17 emo@eclipse.org
1.0
CVSS 4.0 · Vendor: eclipse
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain physical access to USB port
  2. Delivery
    Insert malicious USB audio device
  3. Exploit
    Host enumerates and parses crafted descriptor
  4. Execution
    Trigger out-of-bounds read in _ux_host_class_audio_device_type_get()
  5. Impact
    Corrupt parser state or crash USB host stack

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires physical access (AV:P) to a USB port of a device running ThreadX/USBX as a USB HOST, which must enumerate an attacker-supplied USB AUDIO class device so that _ux_host_class_audio_device_type_get() parses the crafted (malformed) audio descriptor. Limiting factors: physical presence to insert the device, high attack complexity (AC:H) to craft a descriptor that reliably triggers the out-of-bounds read, affected versions are USBX before 6.4.3 (fixed in 6.4.3), and impact is bounded to low integrity/availability with no confidentiality loss - this is not remotely exploitable.

Impact

This is a genuinely low-priority issue despite the presence of public exploit code, and the signals are broadly consistent on that point. The vendor CVSS 4.0 vector (AV:P/AC:H/PR:N/UI:N/VC:N/VI:L/VA:L) yields a base score of only 1.0: exploitation requires PHYSICAL access to the device's USB port, high attack complexity, and the impact is limited to low integrity and low availability with NO confidentiality impact (VC:N). This is important because CWE-125 (out-of-bounds read) is frequently assumed to leak data, but the vendor explicitly rates confidentiality as none - the realistic outcome is a parser fault/crash of the USB host stack (availability) rather than meaningful memory disclosure. EPSS is low at 0.33% (23rd percentile), there is NO CISA KEV listing, and while POC/exploit material is referenced via the GHSA advisory, POC availability is NOT the same as active exploitation. The one tension worth noting: the 'Information Disclosure' tag and the VC:N rating conflict (see data_quality_flags), and a physical-access AV:P flaw is structurally incompatible with any scenario of widespread remote exploitation. Net: not a patch-tonight item; schedule it into normal firmware update cycles for affected embedded products.

Exploit ScenarioDerived

An attacker with physical access crafts a malicious USB audio device presenting a malformed audio descriptor and plugs it into a ThreadX/USBX host. When the host enumerates the device and calls _ux_host_class_audio_device_type_get() to parse the descriptor, the function reads past the buffer bounds, corrupting state or crashing the USB host stack. Public exploit/POC material is referenced in the GHSA advisory, but exploitation is bounded by the requirement for physical device insertion and high complexity.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

An out-of-bounds read in Eclipse ThreadX USBX before 6.4.3 occurs when a device acting as a USB host enumerates an attacker-supplied USB audio class device and _ux_host_class_audio_device_type_get() parses a malformed audio descriptor. Exploitation requires physical access to a USB port (AV:P) and high complexity to craft a descriptor that reliably triggers the over-read, and impact is bounded to low integrity and availability with no confidentiality loss; publicly available exploit code exists, but the EPSS score of 0.33% (23rd percentile) and the assessed vector confirm this is not remotely exploitable and is a low-priority issue.

RemediationAI

Upgrade USBX to 6.4.3 or later - vendor-released patch: 6.4.3 - as documented in the Eclipse ThreadX USBX advisory GHSA-4jc2-x5hv-46fq (https://github.com/eclipse-threadx/usbx/security/advisories/GHSA-4jc2-x5hv-46fq). Where upgrading is not immediately possible, compensating controls should target the physical-access precondition: do not expose USB host ports to untrusted parties or public areas, and where firmware and product design allow, disable USB host audio class support (UX_HOST_CLASS_AUDIO or equivalent build-time configuration) so _ux_host_class_audio_device_type_get() is never reachable - the trade-off being loss of USB audio device support on that host. USB port filtering or an authorized-device allowlist can also block unknown audio class devices, at the cost of operational friction for legitimately hot-plugged peripherals. Note that no remote or network mitigation exists, since exploitation requires physically attaching a crafted USB audio device to a host running the vulnerable USBX.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

USBX is the USB support module shipped with Eclipse Foundation ThreadX; the flaw is a CWE-125 out-of-bounds read in the host-side audio class driver routine _ux_host_class_audio_device_type_get(), which walks USB audio class descriptors supplied by an attached peripheral. Because descriptor contents are attacker-controlled when a malicious or malformed USB audio device is plugged in, the routine can read past the end of the parsed buffer. The affected component is identified by CPE cpe:2.3:o:eclipse:threadx_usbx:*:*:*:*:*:*:*:*, i.e. all USBX releases prior to 6.4.3. The supplied CVSS 4.0 vector (AV:P/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L) and the independent CVSS 3.1 assessment (AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L) agree that the attack surface is the physical USB host port, exploitation is complex, and no confidentiality impact results.

Know when Threadx Usbx gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (eclipse) PRIMARY 1.0 LOW
CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 3.1 LOW

Physical USB insertion (AV:P), crafted-descriptor reliability makes AC:H; no auth (PR:N); OOB read yields no confidentiality (C:N) but low integrity/availability from parser corruption/crash.

3.1 AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
4.0 AV:P/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (eclipse).

CVSS VectorVendor: eclipse

Attack Vector
Physical
Attack Complexity
High
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

In USBX before 6.4.3, the USB support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _ux_host_class_audio_device_type_get() when parsing a descriptor of an USB audio device.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Medium
Widely-used embedded RTOS USB stack, but host audio class is a niche code path
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
Poc
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Low

Priority Score

25
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +5
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:o:eclipse:threadx_usbx:*:*:*:*:*:*:*:*
CVE-2022-36063 CRITICAL POC
9.8 Oct 10

Azure RTOS USBx is a USB host, device, and on-the-go (OTG) embedded stack, fully integrated with Azure RTOS ThreadX and

CVE-2023-48698 CRITICAL
9.8 Dec 05

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS Thre

CVE-2023-48697 CRITICAL
9.8 Dec 05

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS Thre

CVE-2023-48696 CRITICAL
9.8 Dec 05

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS Thre

CVE-2023-48695 CRITICAL
9.8 Dec 05

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS Thre

CVE-2023-48694 CRITICAL
9.8 Dec 05

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS Thre

CVE-2022-39293 CRITICAL
9.8 Oct 13

Azure RTOS USBX is a high-performance USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated wit

CVE-2022-29246 CRITICAL
9.8 May 24

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack. Rated critical severity (CVSS 9.8), this vuln

CVE-2022-29223 CRITICAL
9.8 May 24

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack. Rated critical severity (CVSS 9.8), this vuln

CVE-2025-55100 LOW POC
2.4 Oct 17

Out-of-bounds read in Eclipse ThreadX USBX before 6.4.3 allows an attacker with physical access to a target device to le

CVE-2025-55099 LOW POC
2.4 Oct 17

An out-of-bounds read in Eclipse ThreadX USBX before 6.4.3 allows an attacker with physical access to a USB host port to

CVE-2025-55095 MEDIUM
4.2 Jan 27

The function _ux_host_class_storage_media_mount() is responsible for mounting partitions on a USB mass storage device. W

References

Advisories & patches

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy