RUSTSEC-2025-0170: `hugepage_rs::dealloc` may allow invalid memory deallocation from safe code

What to do

1. See which version you have: cargo tree -i hugepage-rs (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p hugepage-rs. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example hugepage-rs = "0.1.1") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

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.

References

• Package: crates.io/crates/hugepage-rs
• Advisory: rustsec.org/advisories/RUSTSEC-2025-0170.html
• Report: github.com/cppcoffee/hugepage-rs/issues/5
• Web: github.com/cppcoffee/hugepage-rs/pull/6
• Web: github.com/cppcoffee/hugepage-rs/commit/2b30bdf227f39b1c9ed7af16ea0cc3957f88da18

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.