Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS
Reported November 22, 2025 Issued November 22, 2025 Package thread-amount (crates.io) Type Vulnerability Categories
-
denial-of-service Keywords #memory-leak #handle-leak #resource-exhaustion #windows #macos Aliases
-
[CVE-2025-65947](https://cve.mitre…
Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS
Reported November 22, 2025 Issued November 22, 2025 Package thread-amount (crates.io) Type Vulnerability Categories
-
denial-of-service Keywords #memory-leak #handle-leak #resource-exhaustion #windows #macos Aliases
-
CVE-2025-65947 References
-
https://github.com/jzeuzs/thread-amount/pull/29 CVSS Score 7.7 HIGH CVSS Details
Attack Complexity Low Attack Requirements None Attack Vector Network Privileges Required None Availability Impact to the Subsequent System None Confidentiality Impact to the Subsequent System None Integrity Impact to the Subsequent System None User Interaction None Availability Impact to the Vulnerable System High Confidentiality Impact to the Vulnerable System None Integrity Impact to the Vulnerable System None Exploit Maturity ProofOfConcept Automatable Yes Recovery User Vulnerability Response Effort Low Provider Urgency Green Value Density Diffuse
CVSS Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P/AU:Y/R:U/V:D/RE:L/U:Green Patched
-
>=0.2.2Affected OSes -
windows -
macos -
ios
Affected Functions Version thread_amount::is_single_threaded
-
<0.2.2thread_amount::thread_amount -
<0.2.2
Description
Affected versions of this crate contain resource leaks when querying thread counts on Windows and Apple platforms.
Windows
The thread_amount function calls CreateToolhelp32Snapshot but fails to close the returned HANDLE using CloseHandle. Repeated calls to this function will cause the handle count of the process to grow indefinitely, eventually leading to system instability or process termination when the handle limit is reached.
macOS / iOS
The thread_amount function calls task_threads (via Mach kernel APIs) which allocates memory for the thread list. The function fails to deallocate this memory using vm_deallocate. Repeated calls will result in a steady memory leak, eventually causing the process to be killed by the OOM (Out of Memory) killer.
Impact
Long-running applications (such as servers, daemons, or monitoring tools) that use this crate to periodically check thread counts will eventually crash due to resource exhaustion.
Mitigation
Upgrade to version 0.2.2 or later, which properly releases OS resources.
Advisory available under CC0-1.0 license.