# CVE-2025-1176: GNU Binutils ld elflink.c _bfd_elf_gc_mark_rsec heap-based overflow

> A heap-based buffer overflow in the GNU Binutils linker allows remote attackers to execute arbitrary code or cause denial of service via crafted ELF files.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/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:** 11 Feb 2025
- **Updated:** 11 Apr 2025
- **Also known as:** AZL-56579, AZL-56652, AZL-56655, AZL-86934, BELL-CVE-2025-1176, CLSA-2025-1754649018, CLSA-2025-1760023587, DEBIAN-CVE-2025-1176, ECHO-adcd-7287-f168, GHSA-9373-29x4-fjwq, ROOT-OS-DEBIAN-12-CVE-2025-1176, UBUNTU-CVE-2025-1176

## What is CVE-2025-1176?

CVE-2025-1176 is a low-severity memory corruption vulnerability in Gnu Binutils, published on 11 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 was found in GNU Binutils 2.43 and classified as critical. This issue affects the function _bfd_elf_gc_mark_rsec of the file elflink.c of the component ld. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The patch is named f9978defb6fab0bd8583942d97c112b0932ac814. It is recommended to apply a patch to fix this issue.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Gnu Binutils.

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

Apply the vendor's patch.

## Is CVE-2025-1176 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1176 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-1176 and fix it if it is affected.

What it is: CVE-2025-1176 is a low-severity memory corruption vulnerability in Gnu Binutils, published on 11 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-1176 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-1176/ (Markdown: https://insights.sbomify.com/CVE-2025-1176/index.md)
```

## Sources

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

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