CVE-2025-5702

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.

Published: 2025-06-05 Last update: 2025-10-01 Assigner: 3ff69d7a-14f2-4f67-a097-88dee7810d18 Source: 3ff69d7a-14f2-4f67-a097-88dee7810d18
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-5702 is rated Moderate Risk (41/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.29%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-5702

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-01 0.05% 0.29% +0.24%
2 2026-02-08 0.05% 0.05% +0.01%
3 2025-11-21 — 0.05% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-5702

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.6 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.2 3.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-5702

OS Trackers for CVE-2025-5702

vendor priority summary link
debian unimportant CVE-2025-5702 unimportant priority: Debian including 1 source packages (glibc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-5702
redhat medium — https://access.redhat.com/security/cve/CVE-2025-5702
suse high CVE-2025-5702 severity important: SUSE including 251 source package names (glibc, glibc-2.34-168.el9_6.20, …), 538 product×package rows across 40 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Liberty Linux 9, … (40 product lines)): Known Not Affected 306, Fixed 232. https://www.suse.com/security/cve/CVE-2025-5702/
ubuntu medium CVE-2025-5702 medium priority: Ubuntu including 2 source packages (eglibc, glibc), 14 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, trusty, upstream, xenial): not-affected 5, DNE 4, needs-triage 2, released 2, ignored 1. https://ubuntu.com/security/CVE-2025-5702

Affected software / configurations for CVE-2025-5702

Vendor Product Version Raw CPE
gnu glibc >= 2.39, < 2.39-209 cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*
gnu glibc >= 2.40, < 2.40-139 cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*
gnu glibc >= 2.41, < 2.41-60 cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*

References for CVE-2025-5702

cvelogic Threat Intelligence