Skip to main content
VulnerabilityPublished

Heapless: `Spsc::peek` used `Relaxed` ordering where it should have use `Acquire`

Affects heaplessSource GCVE Database

0
Severity
High

Rated High by Threat Radar's AI analysis

Patch
Available – fixed in 0.9.4

Data as of 19 Nov 2026, 09:50 UTC

What to do

Upgrade heapless to 0.9.4.

Affected software

ProductAffectedFixed in
crates.ioheaplesspkg:cargo/heaplessOther threatsAffected
  • >=0.0.0-0 <0.9.4
Fixed in
  • 0.9.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to heapless version 0.9.4 or later, where the issue has been fixed by correcting the memory ordering in Spsc::peek. No other mitigation is required.

Description

A concurrency issue in the heapless crate's Spsc::peek method uses Relaxed memory ordering instead of the correct Acquire ordering, potentially causing undefined behavior due to a race condition. This flaw was reported by Jacob Finkelman and affects versions prior to 0.9.4. A fix is available in version 0.9.4.

References

Community reviews

Loading reviews…