https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-07T14:02:12.312049+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cnvd-2021-71650 cnvd-2021-71650 2026-10-07T14:02:12.318524+00:00 cnvd-2021-71650 https://cve.radiocsirt.org/vuln/euvd-2026-48037 EUVD-2026-48037 2026-10-07T14:02:12.318569+00:00 EUVD-2026-48037 https://cve.radiocsirt.org/vuln/fkie_cve-2020-36206 fkie_cve-2020-36206 2026-10-07T14:02:12.318584+00:00

An issue was discovered in the rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, a data race and memory corruption can occur.

 https://cve.radiocsirt.org/vuln/ghsa-9mxw-4856-9cm5 GHSA-9mxw-4856-9cm5 — Data races in rusb 2026-10-07T14:02:12.318617+00:00

Affected: crates.io: rusb

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.

 https://cve.radiocsirt.org/vuln/gsd-2020-36206 gsd-2020-36206 2026-10-07T14:02:12.318646+00:00 gsd-2020-36206 https://cve.radiocsirt.org/vuln/rustsec-2020-0098 RUSTSEC-2020-0098 — UsbContext trait did not require implementers to be Send and Sync. 2026-10-07T14:02:12.318659+00:00

Affected: crates.io: rusb

Affected versions of `rusb` did not require `UsbContext` to implement `Send` and `Sync`. However, through `Device` and `DeviceHandle` it is possible to use `UsbContext`s 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`.