dbcve.org
Threadx UsbxOperating system · Eclipse

CVE-2025-55097

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-17
Fix available
A fix is available. Upgrade to 6.4.3.202503 or later.
See remediation →
66/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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_streaming_sampling_get() when parsing a descriptor of an USB streaming device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A bounds check missing in the USBX library's audio streaming descriptor parsing allows an attacker to trigger an out-of-bounds read in _ux_host_class_audio_streaming_sampling_get() by providing a malformed USB audio device descriptor. This could expose heap or stack memory contents to an attacker controlling a malicious USB device.

MitigationUpdate USBX to version 6.4.3 or later which contains proper bounds validation in the descriptor parsing routine.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Threadx UsbxOperating system
Affected:< 6.4.3.202503

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate USBX library version
    Search for USBX version definition in firmware image, header files (typically ux_version.h or similar), or library manifest. Common locations: /lib/usbx/, embedded firmware binary strings, or build configuration files.
    Affected if USBX version string shows a version lower than 6.4.3.202503
  2. Verify USB host audio class is enabled
    Check build configuration or header defines for UX_HOST_CLASS_AUDIO_ENABLE or similar preprocessor flags. Inspect Makefile or project configuration for audio class compilation.
    Affected if USB host audio streaming class is compiled into the firmware (UX_HOST_CLASS_AUDIO is defined and not commented out)
  3. Confirm USB host mode is active
    Inspect runtime configuration or device tree to confirm the platform is configured in USB host mode (not device-only mode). Look for ux_host_stack_initialize() call with USB host controller initialization.
    Affected if System operates as a USB host accepting external USB device connections
  4. Check for audio streaming descriptor handling code
    Search firmware binary or source for references to _ux_host_class_audio_streaming_sampling_get or UX_HOST_CLASS_AUDIO_STREAMING parsing routines.
    Affected if Audio streaming descriptor parsing code is present in the firmware build

Affected if USBX version is below 6.4.3.202503 AND the USB host audio streaming class is enabled in a USB host configuration, allowing untrusted USB audio devices to be connected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.4.3.202503 or later
Fixed in 6.4.3.202503
Interim mitigation

Update USBX to version 6.4.3 or later which contains proper bounds validation in the descriptor parsing routine.

Recommended fix Moderate confidence

ThreadX USBX version 6.4.3.202503 or later

  1. 1. Identify all embedded devices or projects using ThreadX USBX library versions before 6.4.3.202503
  2. 2. Obtain the latest USBX release (6.4.3.202503 or later) from the Eclipse Foundation ThreadX repository at github.com
  3. 3. Replace the old usbx library binary or source files with the updated version in your build system
  4. 4. Rebuild the firmware or application using the updated USBX library
  5. 5. Retest audio streaming functionality to verify the fix does not introduce regressions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Threadx Usbx Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55097 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data