Unsound sending of non-Send types across threads in threadalone
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Affected versions can run the `Drop` impl of a non-Send type on a different thread than it was created on. The flaw occurs when a stderr write performed by the `threadalone` crate fails, for example because stderr is redirected to a location on a filesystem that is full, or because stderr is a pipe that has been closed by the reader. Dropping a non-Send type on the wrong thread is unsound. If used with a type such as a pthread-based `MutexGuard`, [the consequence is undefined behavior][mutexguard]. If used with `Rc`, there would be a data race on the reference count, which is likewise undefined behavior. [mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | threadalone (crates.io) | before 0.2.1 | 0.2.1 | Patch available | GHSA-w59h-378f-2frm |
- threadalone (crates.io) Vendor— Affected before 0.2.1 Fixed in 0.2.1 Patch available GHSA-w59h-378f-2frm
Remediation
- Fix · GHSA-w59h-378f-2frm threadalone (crates.io) Fixed in 0.2.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-w59h-378f-2frm
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences