dbcve.org
GlibcFramework / library · Gnu

CVE-2025-5702

MEDIUM · 5.6 CVSS v3.1 Published 2025-06-05
Fix available
A fix is available. Upgrade to 2.39-209 / 2.40-139 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable 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
The strcmp implementation optimized for the Power10 processor in the GNU C Library version 2.39 and later writes to vector registers v20 to v31 without saving contents from the caller (those registers are defined as non-volatile registers by the powerpc64le ABI), resulting in overwriting of its contents and potentially altering control flow of the caller, or leaking the input strings to the function to other parts of the program.

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

The Power10-optimized strcmp in glibc 2.39+ writes to non-volatile vector registers v20-v31 without preserving their original contents, violating the powerpc64le ABI. This can corrupt caller-saved state, potentially hijack control flow, or expose sensitive string data to other program parts.

MitigationApply glibc security patches when available, or mitigate by ensuring affected systems do not process untrusted string inputs through the vulnerable strcmp path until patched.

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
GlibcFramework / library
Affected:>= 2.39, < 2.39-209>= 2.40, < 2.40-139>= 2.41, < 2.41-60

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

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

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. Verify system is running on powerpc64le architecture
    Run 'uname -m' and confirm the output is 'ppc64le'. This vulnerability only affects the PowerPC64 Little Endian architecture.
    Affected if Architecture is ppc64le AND glibc version is within affected ranges
  2. Check installed glibc version
    Run 'ldd --version' or '/lib64/libc.so.6 --version' to retrieve the glibc version number.
    Affected if Version is >= 2.39 and < 2.39-209, OR >= 2.40 and < 2.40-139, OR >= 2.41 and < 2.41-60
  3. Confirm glibc library path on the system
    Locate the libc shared library with 'ldd --version' output showing the library path, typically /lib64/libc.so.6 on 64-bit systems.
    Affected if The identified libc.so.6 matches an affected version on a ppc64le system

The system is affected if it runs on powerpc64le architecture with glibc versions 2.39.x before 2.39-209, 2.40.x before 2.40-139, or 2.41.x before 2.41-60.

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 2.39-209 / 2.40-139 / 2.41-60 or later
Fixed in 2.39-2092.40-1392.41-60
Interim mitigation

Apply glibc security patches when available, or mitigate by ensuring affected systems do not process untrusted string inputs through the vulnerable strcmp path until patched.

Recommended fix High confidence

Upgrade glibc to version 2.39-209 or higher, 2.40-139 or higher, or 2.41-60 or higher (ideally the latest stable release in the respective branch)

  1. Identify the current glibc version in use with `ldd --version` or `getconf GNU_LIBC_VERSION`
  2. Determine which major release branch is in use (2.39, 2.40, or 2.41)
  3. Upgrade glibc to the appropriate fixed version: for 2.39.x upgrade to >=2.39-209, for 2.40.x upgrade to >=2.40-139, for 2.41.x upgrade to >=2.41-60
  4. On systems using package managers, apply the relevant security update (e.g., `apt update && apt upgrade` for Debian/Ubuntu, `yum update` for RHEL/CentOS, or equivalent)
  5. Reboot systems if required to load the new glibc library
  6. Verify the new glibc version is installed correctly with `ldd --version`
Caveat glibc upgrades may introduce subtle behavioral changes; test thoroughly, particularly for string comparison and PowerPC64LE applications

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

Fix this in Glibc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
27.0 hours of engineering $4,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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