Advisory

RUSTSEC-2026-0005

Also known as: GHSA-rvr2-r3pv-5m4p

Summary

Potential use-after-free in oneshot when used asynchronously

Details

There is a race condition that can lead to a use-after-free if a oneshot::Receiver is polled but then dropped instead of polled to completion. This could happen if the receiver future was cancelled while receiving, for example by being wrapped in a timeout future or similar.

When the Receiver is polled (Future::poll) it writes a waker to the channel and sets it to the RECEIVING state. If the Receiver was then dropped (instead of polled to completion), the Drop implementation on Receiver unconditionally swapped the channel state to DISCONNECTED and only after doing so it read back its waker from the heap allocation and dropped it. The problem is that the DISCONNECTED state could be observed by the Sender, which would lead to it deallocating the channel heap memory. If the Sender manage to free the channel before the Receiver managed to proceed to dropping the waker, then the Receiver would read from the freed channel memory (use-after-free).

The fix was submitted in https://github.com/faern/oneshot/pull/74 and published as part of oneshot version 0.1.12.

Severity

Not rated by the source.

Dates

Published
2026-01-25 12:00 UTC
Modified
2026-01-27 06:11 UTC

Affected packages and fixes

oneshot

crates.io · All systems

Affected

  • introduced 0.1.2-0, fixed 0.1.12 (semver)

Fixed versions

0.1.12

Fix

  • Fixed version 0.1.12
    cargo update -p oneshot --precise 0.1.12

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