{"answers":{"affected":"1 open source package ship an affected version, including hugepage-rs.","exploited":"There is no known exploitation of RUSTSEC-2025-0170 in the wild and no public exploit code.","fix":"Upgrade hugepage-rs to 0.1.1 or later.","what":"RUSTSEC-2025-0170 is a memory corruption vulnerability in hugepage-rs, published on 24 Apr 2025."},"fix_prompt":"Check this codebase for RUSTSEC-2025-0170 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2025-0170 is a memory corruption vulnerability in hugepage-rs, published on 24 Apr 2025. \nExploitation: There is no known exploitation of RUSTSEC-2025-0170 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hugepage-rs (crates.io): affected from 0.0.0-0; fixed in 0.1.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2025-0170/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0170/index.md)","id":"RUSTSEC-2025-0170","markdown":"https://insights.sbomify.com/RUSTSEC-2025-0170/index.md","name":"RUSTSEC-2025-0170","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust hugepage allocator","requires_auth":"none","summary":"Safe code could trigger undefined behavior via invalid memory deallocation in the hugepage_rs library, potentially leading to crashes or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.\n\n`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\nunsafe preconditions for callers.\n\nAffected 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.\n\nThe upstream repository fixed this in version `0.1.1` by marking `dealloc` as unsafe and documenting the caller's safety requirements.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"`hugepage_rs::dealloc` may allow invalid memory deallocation from safe code","id":"RUSTSEC-2025-0170","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.1.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"hugepage-rs","purl":"pkg:cargo/hugepage-rs","source":"RUSTSEC-2025-0170"}],"products":null,"published":"2025-04-24","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Safe code could trigger undefined behavior via invalid memory deallocation in the hugepage_rs library, potentially leading to crashes or code execution.","url":"https://insights.sbomify.com/RUSTSEC-2025-0170/"}