A malicious coder can get unsound access to TCell or TLCell memory
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
This is impossible to do by accident, but by carefully constructing marker types to be covariant, a malicious coder can cheat the singleton check in `TCellOwner` and `TLCellOwner`, giving unsound access to cell memory. This could take the form of getting two mutable references to the same memory, or a mutable reference and an immutable reference. The fix is for the crate to internally force the marker type to be invariant. This blocks the conversion between covariant types which Rust normally allows.
Why it matters now
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 |
|---|---|---|---|---|---|
| — | qcell (crates.io) | before 0.4.3 | 0.4.3 | Patch available | GHSA-9c9f-7x9p-4wqp |
- qcell (crates.io) Vendor— Affected before 0.4.3 Fixed in 0.4.3 Patch available GHSA-9c9f-7x9p-4wqp
Remediation
- Fix · GHSA-9c9f-7x9p-4wqp qcell (crates.io) Fixed in 0.4.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-9c9f-7x9p-4wqp
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences