Process instability via eventfd double close
Published Feb 5, 2025 · Updated Mar 17, 2026
Resource-management error in libcurl for curl 8.11.1 allows remote attackers to destabilize processes after threaded name resolution. An incorrect conditional leaves socketpair-era cleanup in place, so connection teardown closes the inter-thread eventfd twice. The flaw requires a 64-bit eventfd build with the threaded resolver, and the closely spaced close calls constrain control over a reused descriptor.
Summary
What happened
Resource-management error in libcurl for curl 8.11.1 allows remote attackers to destabilize processes after threaded name resolution. An incorrect conditional leaves socketpair-era cleanup in place, so connection teardown closes the inter-thread eventfd twice. The flaw requires a 64-bit eventfd build with the threaded resolver, and the closely spaced close calls constrain control over a reused descriptor.
The record
- CVE
- CVE-2025-0665
- Published
- Feb 5, 2025
- Updated
- Mar 17, 2026
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-1341, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2025CVE publishedPublication date reported by the CVE source.
- Mar 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.11.1 <=8.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo