# CVE-2025-1152: GNU Binutils ld xstrdup.c xstrdup memory leak

> A memory leak in the GNU Binutils linker allows remote attackers to cause a denial of service via high-complexity exploitation.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** AZL-56567, AZL-56573, AZL-56582, AZL-56597, AZL-56621, AZL-56624, AZL-56643, AZL-56645, AZL-56658, BELL-CVE-2025-1152, DEBIAN-CVE-2025-1152, ECHO-cb40-96f7-51cc, GHSA-xr98-5c2m-hfwp, UBUNTU-CVE-2025-1152

## What is CVE-2025-1152?

CVE-2025-1152 is a low-severity denial of service vulnerability in Gnu Binutils, published on 10 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic has been found in GNU Binutils 2.43. Affected is the function xstrdup of the file xstrdup.c of the component ld. The manipulation leads to memory leak. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2025-1152?

It affects 1 product.


Products: Gnu Binutils.

## How do I fix CVE-2025-1152?

Apply the vendor's patch.

## Is CVE-2025-1152 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1152 exists.

## Other vulnerabilities in Gnu Binutils

- [CVE-2017-7614](https://insights.sbomify.com/CVE-2017-7614/): Null dereference in n/a (critical 9.8)
- [CVE-2014-9939](https://insights.sbomify.com/CVE-2014-9939/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7226](https://insights.sbomify.com/CVE-2017-7226/): Information disclosure in n/a (critical 9.1)
- [CVE-2017-6969](https://insights.sbomify.com/CVE-2017-6969/): Information disclosure in n/a (critical 9.1)
- [CVE-2020-19726](https://insights.sbomify.com/CVE-2020-19726/): Denial of service in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1152 and fix it if it is affected.

What it is: CVE-2025-1152 is a low-severity denial of service vulnerability in Gnu Binutils, published on 10 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1152 exists.

Affected product: Gnu Binutils. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1152/ (Markdown: https://insights.sbomify.com/CVE-2025-1152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1152
- OSV: https://osv.dev/vulnerability/CVE-2025-1152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1152/
Summaries are generated and may contain mistakes; the official description above is the record.