RUSTSEC-2026-0274 json
Double free / use-after-free in `ReadChunk::commit` when an element's `Drop` panics
published 3mo ago modified 2mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
`ReadChunk::commit` and `ReadChunk::commit_all` drop the committed elements before advancing the consumer head. If an element's `Drop` panics during the drop loop, `head` is never advanced, so the ring buffer still treats those slots as holding live elements. When the `RingBuffer` is later dropped (it walks `head..tail` and drops each slot), or a subsequent `read_chunk()` / `commit()` touches the same slots, the already-dropped elements are dropped a second time — a double free (CWE-415) / use-after-free (CWE-416) reachable from safe Rust.
## Mitigation
Update to 0.3.5 (0.3.x line) or 0.4.0. Note that 0.4.0 contains a behavior change in `is_abandoned()`, so users on 0.3.x should prefer 0.3.5.
Patch / fix
- crates.io rtrb 0.3.5, 0.4.0
Is RUSTSEC-2026-0274 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | rtrb | >=0.0.0-0, <0.3.5 >=0.4.0-0, <0.4.0 |
0.3.5 0.4.0 |
References
-
crates.io
/crates/rtrb
package
-
rustsec.org
/advisories/RUSTSEC-2026-0274.html
advisory
-
github.com
/mgeier/rtrb/issues/185
report
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.