Skip to content
Fencer Intel
medium —

GHSA-g23h-7vf9-xc25 json

Mimalloc Can Allocate Memory with Bad Alignment

published 3y ago modified 2mo ago also RUSTSEC-2022-0094

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

This crate depended on a promise regarding alignments made by the author of the mimalloc allocator to avoid using aligned allocation functions where possible for performance reasons. Since then, the mimalloc allocator's logic changed, making it break this promise. This caused this crate to return memory with an incorrect alignment for some allocations, particularly those with large alignments. The flaw was fixed by always using the aligned allocation functions.

Patch / fix

  • crates.io mimalloc 0.1.39

Is GHSA-g23h-7vf9-xc25 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io mimalloc
<0.1.39
>=0.0.0-0, <0.1.39
0.1.39

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.