`IterMut` violates Stacked Borrows by invalidating internal pointer
Priority LOW 38CWE-476Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-476.
Summary
Affected versions of this crate contain a soundness issue in the `IterMut` iterator implementation. The `IterMut::next` and `IterMut::next_back` methods temporarily create an exclusive reference to the key when dereferencing the internal node pointer. This invalidates the shared pointer held by the internal `HashMap`, violating Stacked Borrows rules.
Why it matters now
Fix Fixed lru (crates.io): 0.16.3
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 |
|---|---|---|---|---|---|
| — | lru (crates.io) | 0.9.0 to before 0.16.3 | 0.16.3 | Patch available | GHSA-rhfx-m35p-ff5j |
- lru (crates.io) Vendor— Affected 0.9.0 to before 0.16.3 Fixed in 0.16.3 Patch available GHSA-rhfx-m35p-ff5j
Remediation
- Fix · GHSA-rhfx-m35p-ff5j lru (crates.io) Fixed in 0.16.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-rhfx-m35p-ff5j
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences