RUSTSEC-2026-0254

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2026-0254

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0254.json

JSON Data

https://api.test.osv.dev/v1/vulns/RUSTSEC-2026-0254

Published

2026-08-11T12:00:00Z

Modified

2026-08-12T10:30:16.681864238Z

Summary

Panic-safety unsoundness in `Chunk` and `InlineArray` (use-after-free / double-free)

Details

Several methods in sp-sized-chunks drop elements before updating the container's length/boundary metadata. If an element's Drop panics during the drop, the metadata update is skipped, so the container still treats the already-dropped elements as live. When the container is later dropped, its own Drop re-visits those slots and drops the freed elements again — a use-after-free / double-free reachable from safe Rust.

sp-sized-chunks is a fork of sized-chunks (companion advisory filed separately) and carries the same bug. The repository is archived and the crate is still on 0.1.0 with no fix available.

Impact

CWE-415 (Double Free): the same allocation is freed twice (e.g. an element holding Box<T>).
CWE-416 (Use-After-Free): an element reads its own freed allocation during Drop (e.g. String) — confirmed under AddressSanitizer.

All are reachable from safe Rust via catch_unwind with element types whose Drop can panic.

Database specific

{
    "license": "CC0-1.0"
}

References

Affected packages

crates.io / sp-sized-chunks

Package

Name: sp-sized-chunks; View open source insights on deps.dev
Purl: pkg:cargo/sp-sized-chunks

Affected ranges

Type: SEMVER
Events: Introduced

0.0.0-0

Ecosystem specific

{
    "affects": {
        "os": [],
        "functions": [
            "sp_sized_chunks::Chunk::clear",
            "sp_sized_chunks::Chunk::drop_left",
            "sp_sized_chunks::Chunk::drop_right",
            "sp_sized_chunks::InlineArray::clear"
        ],
        "arch": []
    },
    "affected_functions": null
}