Advisory

RUSTSEC-2025-0170

Also known as: None

Summary

hugepage_rs::dealloc may allow invalid memory deallocation from safe code

Details

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.

Severity

Not rated by the source.

Dates

Published
2025-04-24 12:00 UTC
Modified
2026-08-12 09:45 UTC

Affected packages and fixes

hugepage-rs

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.1.1 (semver)

Fixed versions

0.1.1

Fix

  • Fixed version 0.1.1
    cargo update -p hugepage-rs --precise 0.1.1

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