Slock<T> allows sending non-Send types across thread boundaries
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
`Slock<T>` unconditionally implements `Send`/`Sync`. Affected versions of this crate allows sending non-Send types to other threads, which can lead to data races and memory corruption due to the data race.
Why it matters now
Fix Fixed slock (crates.io): 0.2.0
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 |
|---|---|---|---|---|---|
| — | slock (crates.io) | before 0.2.0 | 0.2.0 | Patch available | GHSA-83r8-p8v6-6gfm |
- slock (crates.io) Vendor— Affected before 0.2.0 Fixed in 0.2.0 Patch available GHSA-83r8-p8v6-6gfm
Remediation
- Fix · GHSA-83r8-p8v6-6gfm slock (crates.io) Fixed in 0.2.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-83r8-p8v6-6gfm
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences