AtomicBucket<T> unconditionally implements Send/Sync
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
In the affected versions of the crate, `AtomicBucket<T>` unconditionally implements `Send`/`Sync` traits. Therefore, users can create a data race to the inner `T: !Sync` by using the `AtomicBucket::data_with()` API. Such data races can potentially cause memory corruption or other undefined behavior. The flaw was fixed in commit 8e6daab by adding appropriate Send/Sync bounds to the Send/Sync impl of struct `Block<T>` (which is a data type contained inside `AtomicBucket<T>`).
Why it matters now
Fix Fixed metrics-util (crates.io): 0.7.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 |
|---|---|---|---|---|---|
| — | metrics-util (crates.io) | before 0.7.0 | 0.7.0 | Patch available | GHSA-3hxh-7jxm-59x4 |
- metrics-util (crates.io) Vendor— Affected before 0.7.0 Fixed in 0.7.0 Patch available GHSA-3hxh-7jxm-59x4
Remediation
- Fix · GHSA-3hxh-7jxm-59x4 metrics-util (crates.io) Fixed in 0.7.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-3hxh-7jxm-59x4
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences