Rust advisories / rusb
Unsound HighRUSTSEC-2020-0098 · rusb
RUSTSEC-2020-0098: UsbContext trait did not require implementers to be Send and Sync.
Short answerrusb has an API that can cause undefined behaviour from safe code: UsbContext trait did not require implementers to be Send and Sync.. Fixed in 0.7.0.
| Crate | rusb |
|---|---|
| Type | Unsound (memory-corruption, thread-safety) |
| Affected versions | Before 0.7.0. |
| Fixed in | 0.7.0 |
| Severity | High, CVSS 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-12-18 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36206, GHSA-9mxw-4856-9cm5 |
What to do
- See which version you have:
cargo tree -i rusb(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p rusb. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplerusb = "0.7.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Affected versions of rusb did not require UsbContext to implement Send and Sync. However, through Device and DeviceHandle it is possible to use UsbContexts across threads.
This issue allows non-thread safe UsbContext types to be used concurrently leading to data races and memory corruption.
The issue was fixed by adding Send and Sync bounds to UsbContext.
References
- Package: crates.io/crates/rusb
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0098.html
- Report: github.com/a1ien/rusb/issues/44
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?