# CVE-2025-0665: eventfd double close

> libcurl incorrectly closes an eventfd twice during connection teardown, potentially causing a denial of service.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Feb 2025
- **Updated:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2025-0665, AZL-56692, BELL-CVE-2025-0665, CLEANSTART-2026-VM75462, CURL-CVE-2025-0665, DEBIAN-CVE-2025-0665, GHSA-cc57-hgv8-p56r, JLSEC-2026-421, MINI-9p7h-6f7r-988m, openSUSE-SU-2025:14809-1

## What is CVE-2025-0665?

CVE-2025-0665 is a high-severity vulnerability in Haxx Curl, published on 5 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libcurl would wrongly close the same eventfd file descriptor twice when taking
down a connection channel after having completed a threaded name resolve.

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

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `curl` | openSUSE:Tumbleweed | All versions | 8.12.1-1.1 |

Products: Haxx Curl, Netapp Bootstrap Os, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware.

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

Upgrade to a fixed version.

## Is CVE-2025-0665 being exploited?

There is no known exploitation of CVE-2025-0665 in the wild and no public exploit code.

## Other vulnerabilities in Haxx Curl

- [CVE-2026-19931](https://insights.sbomify.com/CVE-2026-19931/): Negotiate ambient user conn reuse (critical 9.8)
- [CVE-2026-10536](https://insights.sbomify.com/CVE-2026-10536/): HTTP/2 stream-dependency tree UAF (critical 9.8)
- [CVE-2026-11856](https://insights.sbomify.com/CVE-2026-11856/): cross-origin Digest auth state leak (critical 9.8)
- [CVE-2026-8925](https://insights.sbomify.com/CVE-2026-8925/): SASL double-free (critical 9.8)
- [CVE-2026-9079](https://insights.sbomify.com/CVE-2026-9079/): stale proxy password leak (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0665 is a high-severity vulnerability in Haxx Curl, published on 5 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0665 in the wild and no public exploit code.

Affected product: Haxx Curl. 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-0665/ (Markdown: https://insights.sbomify.com/CVE-2025-0665/index.md)
```

## Sources

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

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