GHSA-fp5x-7m4q-449f Direct Ring Buffer has uninitialized memory exposure in create_ring_buffer
Uninitialized memory exposure in create_ring_buffer allows undefined behavior, potentially leading to code execution or information disclosure.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-fp5x-7m4q-449f?
GHSA-fp5x-7m4q-449f is a memory corruption vulnerability in direct_ring_buffer, published on 21 Oct 2025.
Official 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.
Which versions are affected by GHSA-fp5x-7m4q-449f?
3 open source packages ship an affected version, including direct_ring_buffer.
| Package | Affected | Fixed in |
|---|---|---|
direct_ring_buffer crates.io | All versions | 0.2.2 |
direct_ring_buffer crates.io | All versions | 0.2.2 |
direct_ring_buffer crates.io | From 0.0.0-0 | 0.2.2 |
How do I fix GHSA-fp5x-7m4q-449f?
Upgrade direct_ring_buffer to 0.2.2 or later.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is GHSA-fp5x-7m4q-449f being exploited?
There is no known exploitation of GHSA-fp5x-7m4q-449f in the wild and no public exploit code.
Sources
Also known as RUSTSEC-2025-0105.