{"id":"RUSTSEC-2026-0293","aliases":[],"status":"published","title":"Double free / use-after-free in `Consumer::skip` and `Consumer::clear` when an element's `Drop` panics","description":"`Consumer::skip()` and `Consumer::clear()` are not panic-safe. They drop the\nconsumed elements in place and only afterwards call `advance_read_index()` to move\nthe ring buffer's read index past them. If an element's `Drop` panics mid-loop,\n`advance_read_index()` is never reached, so the read index still points at the\nalready-dropped elements. When the ring buffer is later dropped, its destructor\nre-visits those slots and drops the same elements a second time — a double free\n(CWE-415) / use-after-free (CWE-416) reachable from safe Rust, confirmed under\nAddressSanitizer.\n\n`Consumer::clear()` delegates to `Consumer::skip(self.len())`, so both share the\nsame root cause and the same fix.\n\n## Mitigation\n\nUpdate to 0.5.2 or later (fixed in agerasev/ringbuf#60).","facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-09-21T12:00:00Z","modified":"2026-09-21T09:15:02Z","fixes":[{"ecosystem":"crates.io","package":"ringbuf","fixed_in":["0.5.2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"crates.io","package":"ringbuf","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.5.2"}]}]}],"references":[{"url":"https://crates.io/crates/ringbuf","tags":["package"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2026-0293.html","tags":["advisory"]},{"url":"https://github.com/agerasev/ringbuf/pull/60","tags":["web"]}],"sources":{"osv":[{"id":"RUSTSEC-2026-0293","title":"Double free / use-after-free in `Consumer::skip` and `Consumer::clear` when an element's `Drop` panics","description":"`Consumer::skip()` and `Consumer::clear()` are not panic-safe. They drop the\nconsumed elements in place and only afterwards call `advance_read_index()` to move\nthe ring buffer's read index past them. If an element's `Drop` panics mid-loop,\n`advance_read_index()` is never reached, so the read index still points at the\nalready-dropped elements. When the ring buffer is later dropped, its destructor\nre-visits those slots and drops the same elements a second time — a double free\n(CWE-415) / use-after-free (CWE-416) reachable from safe Rust, confirmed under\nAddressSanitizer.\n\n`Consumer::clear()` delegates to `Consumer::skip(self.len())`, so both share the\nsame root cause and the same fix.\n\n## Mitigation\n\nUpdate to 0.5.2 or later (fixed in agerasev/ringbuf#60).","status":"published","published":"2026-09-21T12:00:00Z","modified":"2026-09-21T09:15:02.8956642Z","updated_at":"2026-11-02T15:53:40.430679Z"}]}}