GHSA-vfvv-c25p-m7mm

InlineVec::clear() and SerVec::clear() in rkyv were not panic-safe. Both functions iterate over their elements and call drop_in_place on each, updating self.len only after the loop. If an element's Drop implementation panics during the loop, self.len is left at its original value.

A subsequent invocation of clear() on the same container then re-visits the already-freed elements:

InlineVec::clear() is called again from InlineVec's own Drop implementation when the value is later dropped.
SerVec::clear() is called again by SerVec::with_capacity() after the user closure returns.

Technical Impact

CWE-415 (Double Free): Heap corruption when element type holds Box<T>
CWE-416 (Use-After-Free): Memory corruption when element reads from heap during Drop

Both vulnerabilities are triggerable entirely from safe Rust via std::panic::catch_unwind and require no special privileges.

Database specific

{
    "cwe_ids": [
        "CWE-415",
        "CWE-416"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-15T18:09:10Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
}

References

Affected packages

crates.io / rkyv

Package

Name: rkyv; View open source insights on deps.dev
Purl: pkg:cargo/rkyv

Affected ranges

Type: SEMVER
Events: Introduced

0.8.0

Fixed

0.8.16

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-vfvv-c25p-m7mm/GHSA-vfvv-c25p-m7mm.json"