Advisory

RUSTSEC-2025-0042

Also known as: GHSA-xrrq-rrgq-h89w

Summary

Uninitialized read after allocating MemBump

Details

The affected function, MemBump::new(), would allocate memory without
initializing it. Subsequently calling the created value's various alloc
methods would then read and write the start of that memory as a Cell which is
undefined behavior. Instead, it should zero initialize the start of the
allocated memory.

For instance, some values could violate the internal invariants of the type and
cause an assertion failure. Nevertheless, no deterministic read is known to
cause further uninitialized memory to be exposed.

Affected downstream users that can not upgrade are advised to call
MemBump::reset immediately after allocation to manually perform the missing
write of the counter best-as-possible.

The flaw was corrected in commit d8d6a7d096d3aaafd963b356a8f1bbd8d26fd967 by
zeroing the Cell at the start of the allocated memory.

Severity

Not rated by the source.

Dates

Published
2025-07-11 12:00 UTC
Modified
2025-10-28 06:29 UTC

Affected packages and fixes

static-alloc

crates.io · All systems

Affected

  • introduced 0.2.2-0, fixed 0.2.6 (semver)

Fixed versions

0.2.6

Fix

  • Fixed version 0.2.6
    cargo update -p static-alloc --precise 0.2.6

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences