spin-rs initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers
Priority LOW 38Published · 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
`Once::try_call_once` is unsound if invoked more than once concurrently and any call fails to initialise successfully.
Why it matters now
Fix Fixed spin (crates.io): 0.9.8
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 |
|---|---|---|---|---|---|
| — | spin (crates.io) | 0.9.3 to before 0.9.8 | 0.9.8 | Patch available | GHSA-2qv5-7mw5-j3cg |
- spin (crates.io) Vendor— Affected 0.9.3 to before 0.9.8 Fixed in 0.9.8 Patch available GHSA-2qv5-7mw5-j3cg
Remediation
- Fix · GHSA-2qv5-7mw5-j3cg spin (crates.io) Fixed in 0.9.8 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-2qv5-7mw5-j3cg
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences