Compiler Removal of Code to Clear Buffers Affecting glibc package, versions [2.39,]
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-UNMANAGED-GLIBC-10667940
- published10 Jul 2025
- disclosed5 Jun 2025
- creditUnknown
Introduced: 5 Jun 2025
CVE-2025-5745 (opens in a new tab)How to fix?
A fix was pushed into the master branch but not yet published.
Overview
Affected versions of this package are vulnerable to Compiler Removal of Code to Clear Buffers due to the strncmp implementation optimized for the Power10 processor. An attacker can alter the control flow of the caller or leak sensitive input strings to other parts of the program. This occurs because glibc writes to vector registers v20 to v31, which are defined as non-volatile registers, without saving contents from the caller, resulting in overwriting of their contents.
Note: This issue is identical to CVE-2025-5702, and was introduced introduced due to code being copied over from strcmp.
Workaround
This vulnerability can be mitigated by disabling the Power10 optimized string routines in glibc, 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