GHSA-w59h-378f-2frm
Unsound sending of non-Send types across threads in threadalone
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. If used with Rc, there would be a data race on the
reference count, which is likewise undefined behavior.
What each source reports
GitHub AdvisoriesNo score
Unsound sending of non-Send types across threads in threadalone
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. If used with Rc, there would be a data race on the
reference count, which is likewise undefined behavior.
- Record
GHSA-w59h-378f-2frm- Updated
- 2026-11-02
OSVNo score
Unsound sending of non-Send types across threads in threadalone
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. If used with Rc, there would be a data race on the
reference count, which is likewise undefined behavior.
- Record
GHSA-w59h-378f-2frm- Updated
- 2026-11-02
OSVRUSTSEC-2024-0005No score
Unsound sending of non-Send types across threads
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. If used with Rc, there would be a data race on the
reference count, which is likewise undefined behavior.
- Record
RUSTSEC-2024-0005- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
threadalonecrates.io | before 0.2.1 | 0.2.1 |
threadalonecrates.io | 0.0.0-0 up to 0.2.1 | 0.2.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-w59h-378f-2frm is a vulnerability with no CVSS score yet in threadalone, published January 7, 2024. No source lists public exploit code. Fixed in threadalone 0.2.1.