PT-2025-46130 · Crates.Io · Direct Ring Buffer

Published

2025-10-21

·

Updated

2025-10-21

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
The safe function create ring buffer allocates a buffer using Vec::with capacity followed by set len, creating a Box<[T]> containing uninitialized memory.
This leads to undefined behavior when functions like write slices create typed slices (e.g., &mut [bool]) over the uninitialized memory, violating Rust's validity invariants. The issue has been confirmed using Miri.
Fixed in version 0.2.2 by using resize with to properly initialize the buffer with T::default(), adding a T: Default bound to ensure sound initialization.
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

RUSTSEC-2025-0105

Affected Products

Direct Ring Buffer