GHSA-rhfx-m35p-ff5j json
`IterMut` violates Stacked Borrows by invalidating internal pointer
published 10mo ago modified 2mo ago also RUSTSEC-2026-0002
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
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.
Patch / fix
Is GHSA-rhfx-m35p-ff5j in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | lru | >=0.9.0, <0.16.3 |
0.16.3 |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/jeromefroe/lru-rs/pull/224
web
-
github.com
/jeromefroe/lru-rs
package
-
rustsec.org
/advisories/RUSTSEC-2026-0002.html
web, advisory
-
crates.io
/crates/lru
package
Sources
- GitHub Advisory GHSA-rhfx-m35p-ff5j
- OSV RUSTSEC-2026-0002
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.