Advisory

RUSTSEC-2026-0122

Also known as: GHSA-vfvv-c25p-m7mm

Summary

Potential use-after-free due to lack of panic safety in InlineVec::clear and SerVec::clear

Details

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.

Impact

  • CWE-415 (Double Free): heap corruption when the element type is one that owns memory, such as Box<T> or Vec<T>
  • CWE-416 (Use-After-Free): memory corruption when an element is accessed following a caught panic

Both types of undefined behavior can be invoked in safe Rust, but only if
unwinding panics are enabled and std::panic::catch_unwind is used.

Severity

Not rated by the source.

Dates

Published
2026-04-23 12:00 UTC
Modified
2026-05-16 07:08 UTC

Affected packages and fixes

rkyv

crates.io · All systems

Affected

  • introduced 0.8.0, fixed 0.8.16 (semver)

Fixed versions

0.8.16

Fix

  • Fixed version 0.8.16
    cargo update -p rkyv --precise 0.8.16

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