What is GHSA-FP5X-7M4Q-449F?

GHSA-FP5X-7M4Q-449F is a low-severity security vulnerability in direct_ring_buffer (rust), affecting versions < 0.2.2. It is fixed in 0.2.2.

Which versions of direct_ring_buffer are affected by GHSA-FP5X-7M4Q-449F?

direct_ring_buffer (rust) versions < 0.2.2 is affected.

Is there a fix for GHSA-FP5X-7M4Q-449F?

Yes. GHSA-FP5X-7M4Q-449F is fixed in 0.2.2. Upgrade to this version or later.

Is GHSA-FP5X-7M4Q-449F exploitable, and should I be worried?

Whether GHSA-FP5X-7M4Q-449F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-FP5X-7M4Q-449F is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-FP5X-7M4Q-449F in direct_ring_buffer

Q: Which versions of direct_ring_buffer are affected by GHSA-FP5X-7M4Q-449F?

direct_ring_buffer (rust) versions < 0.2.2 is affected.

Q: Is there a fix for GHSA-FP5X-7M4Q-449F?

Yes. GHSA-FP5X-7M4Q-449F is fixed in 0.2.2. Upgrade to this version or later.

Q: Is GHSA-FP5X-7M4Q-449F exploitable, and should I be worried?

Whether GHSA-FP5X-7M4Q-449F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-FP5X-7M4Q-449F is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-FP5X-7M4Q-449F?

Upgrade direct_ring_buffer to 0.2.2 or later.

Summary

Direct Ring Buffer has uninitialized memory exposure in createringbuffer

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.

Impact

Affected versions

direct_ring_buffer (< 0.2.2)

Security releases

direct_ring_buffer → 0.2.2 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade direct_ring_buffer to 0.2.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-FP5X-7M4Q-449F? GHSA-FP5X-7M4Q-449F is a low-severity security vulnerability in direct_ring_buffer (rust), affecting versions < 0.2.2. It is fixed in 0.2.2.
Which versions of direct_ring_buffer are affected by GHSA-FP5X-7M4Q-449F? direct_ring_buffer (rust) versions < 0.2.2 is affected.
Is there a fix for GHSA-FP5X-7M4Q-449F? Yes. GHSA-FP5X-7M4Q-449F is fixed in 0.2.2. Upgrade to this version or later.
Is GHSA-FP5X-7M4Q-449F exploitable, and should I be worried? Whether GHSA-FP5X-7M4Q-449F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-FP5X-7M4Q-449F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-FP5X-7M4Q-449F? Upgrade direct_ring_buffer to 0.2.2 or later.