Advisory

RUSTSEC-2026-0253

Also known as: None

Summary

Potential use-after-free due to lack of panic safety in LruCache::pop()

Details

LruCache::pop() in lru was not panic-safe. If the Drop implementation of a stored key panics during pop(), self.detach() is never called, leaving dangling pointers in the internal doubly-linked list.

A subsequent cache operation that triggers eviction can then dereference these dangling pointers:

  • The node is freed from the map, but remains linked in the LRU list due to the skipped detach() call
  • When a new insertion causes eviction, the LRU traversal encounters the dangling pointer
  • This results in a write to already-freed memory during the eviction process

Impact

  • CWE-416 (Use-After-Free): memory corruption when subsequent cache operations access freed node pointers in the linked list
  • CWE-415 (Double Free): potential heap corruption when the same memory is freed multiple times

Both types of undefined behavior can be invoked in safe Rust, but only if unwinding panics are enabled and std::panic::catch_unwind is used with key types that have potentially-panicking Drop implementations.

Fix

Fixed in lru 0.18.2 by detaching the node from the linked list before freeing it and dropping the key (lru-rs#238).

Severity

Not rated by the source.

Dates

Published
2026-05-12 12:00 UTC
Modified
2026-08-11 11:15 UTC

Affected packages and fixes

lru

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.18.2 (semver)

Fixed versions

0.18.2

Fix

  • Fixed version 0.18.2
    cargo update -p lru --precise 0.18.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences