Rust advisories / slice-ring-buffer
Vulnerability HighRUSTSEC-2025-0044 · slice-ring-buffer
RUSTSEC-2025-0044: Four unique double-free vulnerabilities triggered via safe APIs
Short answerA security vulnerability in the slice-ring-buffer crate: Four unique double-free vulnerabilities triggered via safe APIs. GitHub rates it High. No fixed version: replace the crate or remove the affected code path.
| Crate | slice-ring-buffer |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | High (GitHub rating) |
| Published | 2025-06-16 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-7mcq-f592-pf7v |
| Affected functions | slice_ring_buffer::IntoIter::clone, slice_ring_buffer::SliceRingBuffer::extend_from_slice, slice_ring_buffer::SliceRingBuffer::insert, slice_ring_buffer::SliceRingBuffer::shrink_to_fit |
What to do
- Find who pulls it in:
cargo tree -i slice-ring-buffer. - Avoid the affected API (
slice_ring_buffer::IntoIter::clone,slice_ring_buffer::SliceRingBuffer::extend_from_slice,slice_ring_buffer::SliceRingBuffer::insert,slice_ring_buffer::SliceRingBuffer::shrink_to_fit), or replace the crate.
Details from the advisory
The crate slice-ring-buffer was developed as a fork of slice-deque to continue maintenance and provide security patches, since the latter has been officially unmaintained (RUSTSEC-2020-0158).
While slice-ring-buffer has addressed some previously reported memory safety issues inherited from its fork origin (RUSTSEC-2021-0047), it still retains multiple unresolved memory corruption vulnerabilities.
Specifically, we have discovered four new memory safety bugs, each resulting in double-free violations that can occur when only safe APIs are invoked. These vulnerabilities correspond to four distinct safe APIs in the crate, each exposing unsound and vulnerable behavior due to incorrect usage of unsafe code internally.
Unfortunately, the maintainer doesn't have much availability to resolve these issues so there's no concrete timeline for fixes. Community contributions towards fixing these vulnerabilities would be much appreciated.
References
- Package: crates.io/crates/slice-ring-buffer
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0044.html
- Report: github.com/LiquidityC/slice_ring_buffer/issues/12
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?