RUSTSEC-2026-0002: `IterMut` violates Stacked Borrows by invalidating internal pointer
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
IterMutviolates Stacked Borrows by invalidating internal pointer
| Details | |
|---|---|
| Status | unsound |
| Package | lru |
| Version | 0.12.5 |
| URL | https://github.com/jeromefroe/lru-rs/pull/224 |
| Date | 2026-01-07 |
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.
See advisory page for additional details.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no coreutils file, test, or entry point. Start by checking whether coreutils uses lru 0.12.5, then read the linked lru-rs pull request and the RustSec advisory to determine the required remediation. Done should resolve the affected dependency or otherwise address the soundness issue, with repository validation defined after the dependency path is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100