Double free / use-after-free in Chunk and InlineArray removal methods when an element's Drop panics

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

`Chunk::{clear, drop_left, drop_right}` and `InlineArray::{clear, truncate}` drop the removed elements before updating the metadata that records which slots hold live values — the `left`/`right` index pair for `Chunk`, the length field for `InlineArray`. If an element's `Drop` panics during the drop, that update is never reached, so the collection still treats the already-dropped elements as live. When the collection is later dropped (its destructor walks the range described by the stale metadata), or a subsequent operation touches the same slots, those elements are dropped a second time — a double free (CWE-415) / use-after-free (CWE-416) reachable from safe Rust. The stale field is `left` and `right` for `Chunk::clear`, `left` for `drop_left`, `right` for `drop_right`, and the length field for both `InlineArray` methods.

Mitigation Upgrade to `imbl-sized-chunks` 0.2.0 or later, which commits the metadata before dropping any element (fixed in jneem/imbl-sized-chunks#14, released…

Published by the source

4 Sep 2026, 12:00 UTC

Last modified by the source

21 Sep 2026, 09:15 UTC

Source last checked

23 Oct 2026, 22:04 UTC

1. Revision 1 · created · 24 Oct 2026

   Published from osv record RUSTSEC-2026-0292

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: rustsec-2026-0292

Advisory: Double free / use-after-free in `Chunk` and `InlineArray` removal methods when an element's `Drop` panics
IDs: rustsec-2026-0292
Record: https://patchnext.com/advisories/rustsec-2026-0292 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: imbl-sized-chunks 0.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io imbl-sized-chunks: affected >= 0.0.0-0, < 0.2.0; fixed in 0.2.0

## Suggested inspection (read-only)
- crates.io imbl-sized-chunks: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on imbl-sized-chunks.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0292 (OSV record RUSTSEC-2026-0292 lists affected ranges: crates.io imbl-sized-chunks >=0.0.0-0 <0.2.0 (fixed))

Commands are suggestions: review each one before running it.