Skip to content
OpenAdvisories
Low GHSA-fp5x-7m4q-449f RUSTSEC-2025-0105

Direct Ring Buffer has uninitialized memory exposure in create_ring_buffer

Published Oct 21, 2025 · Updated Oct 28, 2025 · Assigned by GHSA

Description

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.

Affected packages

EcosystemPackageAffectedFixedRecord
crates.io direct_ring_buffer < 0.2.2 0.2.2 GHSA-fp5x-7m4q-449f
crates.io direct_ring_buffer >= 0.0.0-0, < 0.2.2 0.2.2 RUSTSEC-2025-0105

References