Metrics
Affected Vendors & Products
Solution
No solution given by the vendor.
Workaround
One may disable the Power10 optimized string routines in glibc to work around this issue, by setting the glibc.cpu.hwcaps tunable. This can be done by exporting the GLIBC_TUNABLES environment variable like so: export GLIBC_TUNABLES=glibc.cpu.hwcaps=-arch_3_1
Wed, 01 Oct 2025 15:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Gnu
Gnu glibc |
|
CPEs | cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:* | |
Vendors & Products |
Gnu
Gnu glibc |
Mon, 30 Jun 2025 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Redhat
Redhat enterprise Linux |
|
CPEs | cpe:/a:redhat:enterprise_linux:9 cpe:/o:redhat:enterprise_linux:9 |
|
Vendors & Products |
Redhat
Redhat enterprise Linux |
Tue, 17 Jun 2025 16:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
threat_severity
|
threat_severity
|
Fri, 06 Jun 2025 19:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Title | glibc: Vector register overwrite bug in glibc | |
Weaknesses | CWE-404 | |
References |
| |
Metrics |
threat_severity
|
threat_severity
|
Thu, 05 Jun 2025 21:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-665 | |
Metrics |
cvssV3_1
|
Thu, 05 Jun 2025 19:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
References |
|

Status: PUBLISHED
Assigner: glibc
Published:
Updated: 2025-06-05T20:21:44.764Z
Reserved: 2025-06-04T21:57:13.818Z
Link: CVE-2025-5702

Updated: 2025-06-05T20:17:56.516Z

Status : Analyzed
Published: 2025-06-05T19:15:31.073
Modified: 2025-10-01T15:37:50.070
Link: CVE-2025-5702


No data.