Data race in `Iter` and `IterMut`
Priority LOW 38CWE-362Published · Updated
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
In the affected version of this crate, `{Iter, IterMut}::next` used a weaker memory ordering when loading values than what was required, exposing a potential data race when iterating over a `ThreadLocal`'s values. Crates using `Iter::next`, or `IterMut::next` are affected by this issue.
Why it matters now
Fix Fixed thread_local (crates.io): 1.1.4
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 |
|---|---|---|---|---|---|
| — | thread_local (crates.io) | before 1.1.4 | 1.1.4 | Patch available | GHSA-9hpw-r23r-xgm5 |
- thread_local (crates.io) Vendor— Affected before 1.1.4 Fixed in 1.1.4 Patch available GHSA-9hpw-r23r-xgm5
Remediation
- Fix · GHSA-9hpw-r23r-xgm5 thread_local (crates.io) Fixed in 1.1.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-9hpw-r23r-xgm5
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences