Advisory

RUSTSEC-2026-0256

Also known as: None

Summary

Panic-safety unsoundness in truncate_back, truncate_front, clear, and extend_from_slice (use-after-free / double-free)

Details

Several methods in circular-buffer drop elements before updating the buffer's start/end metadata. If an element's Drop panics during the drop, the metadata update is skipped, so the buffer still treats the already-dropped elements as live. When the buffer is later dropped (or used after the panic is caught), those elements are visited again — a use-after-free / double-free reachable from safe Rust.

Impact

  • CWE-415 (Double Free): the same allocation is freed twice.
  • CWE-416 (Use-After-Free): a freed allocation is accessed during a repeated Drop.

Reachable entirely from safe Rust via catch_unwind with element types whose Drop can panic.

Fix

Fixed in circular-buffer 2.0.1 by adjusting the buffer's start/end metadata before the elements are dropped.

Severity

Not rated by the source.

Dates

Published
2026-08-11 12:00 UTC
Modified
2026-08-12 10:30 UTC

Affected packages and fixes

circular-buffer

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 2.0.1 (semver)

Fixed versions

2.0.1

Fix

  • Fixed version 2.0.1
    cargo update -p circular-buffer --precise 2.0.1

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