dbcve.org
ThreadxApplication · Eclipse

CVE-2025-55080

HIGH · 7.1 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 6.4.3 or later.
See remediation →
73/100
Remediation priority · Elevated
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 Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't enough, allowing an attacker to obtain an arbitrary memory read/write.

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

In Eclipse ThreadX RTOS before version 6.4.3, the syscall parameter verification is insufficient even when memory protection is enabled. This allows an attacker to bypass the intended memory protection boundaries and perform arbitrary memory read/write operations through malformed syscall parameters, potentially leading to information disclosure and code execution.

MitigationUpgrade to Eclipse ThreadX version 6.4.3 or later, which contains proper syscall parameter validation. If upgrading is not immediately feasible, review and harden syscall handler parameter bounds checking to ensure all memory references stay within allowed boundaries.

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
ThreadxApplication
Affected:< 6.4.3

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Confirm Eclipse ThreadX RTOS is in use
    Identify if the embedded system is running Eclipse ThreadX as its RTOS. Check system documentation, build configuration files, or boot logs for 'ThreadX' or 'Eclipse ThreadX' references.
    Affected if The system does not use Eclipse ThreadX RTOS, then this CVE does not apply.
  2. Determine the installed ThreadX version
    Locate the ThreadX version in your build artifacts, version header files (commonly tx_version.h or similar), or firmware information. Compare your version against the affected range of versions prior to 6.4.3.
    Affected if Your installed ThreadX version is lower than 6.4.3, indicating the vulnerability is present.
  3. Verify if memory protection is enabled
    Check your ThreadX configuration or build settings for memory protection unit (MPU) settings. Look for MPU_ENABLE, TXM_MODULE_*, or similar configuration flags in your ThreadX configuration file (tx_user.h or build configuration).
    Affected if Memory protection is enabled or disabled does not matter for this CVE - the flaw exists in syscall parameter verification regardless of memory protection being enabled.
  4. Determine if the system uses syscalls
    Review your application code and system design to identify if ThreadX syscalls (TXM_*) are being used for user-mode thread communication or memory management operations.
    Affected if If the system does not use ThreadX syscalls at all, the attack surface for this specific vulnerability may be reduced, though the code flaw still exists in the RTOS.

You are affected if your system runs Eclipse ThreadX RTOS with a version lower than 6.4.3, regardless of memory protection configuration, since the syscall parameter verification flaw exists in the base RTOS code.

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 or later
Fixed in 6.4.3
Interim mitigation

Upgrade to Eclipse ThreadX version 6.4.3 or later, which contains proper syscall parameter validation. If upgrading is not immediately feasible, review and harden syscall handler parameter bounds checking to ensure all memory references stay within allowed boundaries.

Recommended fix Moderate confidence

ThreadX 6.4.3

  1. 1. Identify all deployments and builds using Eclipse ThreadX versions prior to 6.4.3
  2. 2. Obtain Eclipse ThreadX version 6.4.3 or later from the official Eclipse ThreadX repository (github.com/eclipse-threadx)
  3. 3. Update the ThreadX library dependency in your project to version 6.4.3
  4. 4. Rebuild the firmware/application with the updated ThreadX library
  5. 5. Retest the application to ensure functionality is maintained after the upgrade
  6. 6. Deploy the rebuilt firmware to all affected devices

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

Fix this in Threadx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55080 — 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-55080 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