CVE-2020-36206

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.

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.

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`.

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.

Se detectó un problema en la crate rusb versiones anteriores a 0.7.0 para Rust. Debido a una falta de límites de Send y Sync, una carrera de datos y corrupción de la memoria puede ocurrir