RUSTSEC-2025-0170 `hugepage_rs::dealloc` may allow invalid memory deallocation from safe code
Safe code could trigger undefined behavior via invalid memory deallocation in the hugepage_rs library, potentially leading to crashes or code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is RUSTSEC-2025-0170?
RUSTSEC-2025-0170 is a memory corruption vulnerability in hugepage-rs, published on 24 Apr 2025.
Official description
hugepage_rs::dealloc was a publicly accessible safe function. It accepted an arbitrary raw pointer and Layout, then forwarded them to the hugepage allocator's GlobalAlloc::dealloc implementation.
GlobalAlloc::dealloc requires callers to ensure that the pointer denotes a block of memory currently allocated by the allocator and that the layout is the same layout used for the allocation. The safe wrapper neither verified these requirements nor marked them as
unsafe preconditions for callers.
Affected versions therefore allowed safe Rust code to call dealloc with an invalid pointer, a pointer not allocated by the hugepage allocator, or an incorrect layout, which could cause undefined behavior.
The upstream repository fixed this in version 0.1.1 by marking dealloc as unsafe and documenting the caller's safety requirements.
Which versions are affected by RUSTSEC-2025-0170?
1 open source package ship an affected version, including hugepage-rs.
| Package | Affected | Fixed in |
|---|---|---|
hugepage-rs crates.io | From 0.0.0-0 | 0.1.1 |
How do I fix RUSTSEC-2025-0170?
Upgrade hugepage-rs to 0.1.1 or later.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is RUSTSEC-2025-0170 being exploited?
There is no known exploitation of RUSTSEC-2025-0170 in the wild and no public exploit code.