Mimalloc Can Allocate Memory with Bad Alignment
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | mimalloc (crates.io) | before 0.1.39 | 0.1.39 | Patch available | GHSA-g23h-7vf9-xc25 |
- mimalloc (crates.io) Vendor— Affected before 0.1.39 Fixed in 0.1.39 Patch available GHSA-g23h-7vf9-xc25
Remediation
- Fix · GHSA-g23h-7vf9-xc25 mimalloc (crates.io) Fixed in 0.1.39 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-g23h-7vf9-xc25
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences