Advisory

RUSTSEC-2026-0406

Also known as: None

Summary

Use-after-free when changing a multithreaded context with an unfinished frame

Details

When a multithreaded frame (zstdmt feature, CParameter::NbWorkers) is
left unfinished, its jobs may still be running on the worker threads: the C
library only waits for them when the next frame starts, or when the context
is freed. A session reset makes the context accept changes again in the
meantime, so:

  • unloading the dictionary (load_dictionary, ref_cdict, ref_prefix, disable_dictionary, init*, or reset with parameters) freed the dictionary a worker was still compressing against;
  • changing NbWorkers made the next frame resize the job table before waiting for the old jobs.

The flaw was corrected by refusing these calls while a multithreaded frame
is unfinished. The new CCtx::wait_for_workers() waits for the workers
first.

Severity

Not rated by the source.

Dates

Published
2026-10-16 12:00 UTC
Modified
2026-11-02 09:30 UTC

Affected packages and fixes

zstd-safe

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 7.4.0, introduced 8.0.0-0, fixed 8.2.0 (semver)

Fixed versions

7.4.0, 8.2.0

Fix

  • Fixed version 7.4.0
    cargo update -p zstd-safe --precise 7.4.0
  • Fixed version 8.2.0
    cargo update -p zstd-safe --precise 8.2.0

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