{"id":"RUSTSEC-2026-0293","title":"Double free / use-after-free in `Consumer::skip` and `Consumer::clear` when an element's `Drop` panics","summary":"Double free / use-after-free in `Consumer::skip` and `Consumer::clear` when an element's `Drop` panics","severity":"none","vendor":"ringbuf","product":"ringbuf","ecosystem":"rust","affected":["ringbuf >= 0.0.0-0, < 0.5.2"],"patched":["ringbuf 0.5.2"],"published":"2026-09-21","updated":"2026-09-21","sourceUpdated":"2026-09-21T09:15:02.895664200Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2026-0293","references":[{"url":"https://crates.io/crates/ringbuf"},{"url":"https://rustsec.org/advisories/RUSTSEC-2026-0293.html"},{"url":"https://github.com/agerasev/ringbuf/pull/60"}],"tags":["osv","rust"],"ingestedAt":"2026-09-21T16:06:16.786Z","slug":"RUSTSEC-2026-0293","body":"## Overview\n\n`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).\n\n## Affected packages\n\n- `ringbuf >= 0.0.0-0, < 0.5.2`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `ringbuf 0.5.2`","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}