Advisory

RUSTSEC-2025-0125

Also known as: CVE-2025-65947, GHSA-jf9p-2fv9-2jp2

Summary

Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS

Details

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.

Severity

High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Dates

Published
2025-11-22 12:00 UTC
Modified
2025-11-22 12:29 UTC

Affected packages and fixes

thread-amount

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.2.2 (semver)

Fixed versions

0.2.2

Fix

  • Fixed version 0.2.2
    cargo update -p thread-amount --precise 0.2.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences