Skip to content

CVE-2025-65947 thread-amount is Vulnerable to Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS

HighCVSS 8.7 EPSS 0.37%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: partial

Description

thread-amount is a tool that gets the amount of threads in the current process. Prior to version 0.2.2, there are resource leaks when querying thread counts on Windows and Apple platforms. In Windows platforms, 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. In Apple platforms, 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. This issue has been patched in version 0.2.2.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
crates.io thread-amount(crates.io) < 0.2.2; >= 0.0.0-0, < 0.2.2 0.2.2 Fixed
jzeuzs thread-amount = < 0.2.2 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
crates.io thread-amount(crates.io) < 0.2.2 0.2.2
crates.io thread-amount(crates.io) >= 0.0.0-0, < 0.2.2 0.2.2
jzeuzs thread-amount = < 0.2.2 No fix listed

References