Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0293 json

Double free / use-after-free in `Consumer::skip` and `Consumer::clear` when an element's `Drop` panics

published last mo. modified last mo.

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

`Consumer::skip()` and `Consumer::clear()` are not panic-safe. They drop the consumed elements in place and only afterwards call `advance_read_index()` to move the ring buffer's read index past them. If an element's `Drop` panics mid-loop, `advance_read_index()` is never reached, so the read index still points at the already-dropped elements. When the ring buffer is later dropped, its destructor re-visits those slots and drops the same elements a second time — a double free (CWE-415) / use-after-free (CWE-416) reachable from safe Rust, confirmed under AddressSanitizer.

`Consumer::clear()` delegates to `Consumer::skip(self.len())`, so both share the same root cause and the same fix.

## Mitigation

Update to 0.5.2 or later (fixed in agerasev/ringbuf#60).

Patch / fix

  • crates.io ringbuf 0.5.2

Is RUSTSEC-2026-0293 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io ringbuf
>=0.0.0-0, <0.5.2
0.5.2

References

Sources

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.