2495 matches found
CVE-2020-36206
CVE-2020-36206 involves the Rust crate rusb prior to 0.7.0, where the lack of Send and Sync bounds on the UsbContext can enable a data race and memory corruption. The issue is documented across multiple sources (NVD entry and related advisories) and is specifically attributed to not requiring Sen...
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...
CVE-2020-36207
An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur...
CVE-2020-36207
CVE-2020-36207 affects the Rust crate name‑sake “aovec” (Aovec). The root cause is that Aovec does not impose bounds on its Send/Sync traits, which can enable data races and memory corruption when values are used across threads. The vulnerability is documented in multiple sources (e.g., RustSec a...
CVE-2020-36209
CVE-2020-36209 concerns the late-static crate (pre-0.4.0) for Rust. The issue arises because Sync is implemented for LateStatic with T: Send, enabling a data race on a type that is Send but not Sync (e.g., Cell). This can lead to memory corruption or undefined behavior as described in multiple so...
CVE-2020-36209
An issue was discovered in the late-static crate before 0.4.0 for Rust. Because Sync is implemented for LateStatic with T: Send, a data race can occur...
CVE-2020-36211
An issue was discovered in the gfwx crate before 0.3.0 for Rust. Because ImageChunkMut does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur...
CVE-2020-36211
CVE-2020-36211 affects the Rust gfwx crate (pre-0.3.0). The issue is that ImageChunkMut does not have bounds on its Send or Sync traits, allowing data races and memory corruption. Remediation documented in RUSTSEC-2020-0104 and related advisories shows the fix: add T: Send to the Send implementat...
CVE-2020-36214
The CVE-2020-36214 entry concerns the Rust crate multiqueue2 (pre-0.1.7). The root cause is that a non-Send type could be sent to another thread, enabling a data race. Reported in multiple sources (Red Hat, GHSA, OSV/RustSec) and linked advisories confirm the flaw existed across affected versions...
CVE-2020-36214
An issue was discovered in the multiqueue2 crate before 0.1.7 for Rust. Because a non-Send type can be sent to a different thread, a data race can occur...
CVE-2020-36216
An issue was discovered in Input in the eventio crate before 0.5.1 for Rust. Because a non-Send type can be sent to a different thread, a data race and memory corruption can occur...
CVE-2020-36216
CVE-2020-36216 concerns the Rust crate eventio (Input before 0.5.1). A non-Send type could be sent to another thread, enabling a data race and memory corruption. The issue is documented across multiple sources (RustSec/RUSTSEC-2020-0108, GHSA-69VJ-XX27-G45W, Red Hat/CVE references). The root caus...
CVE-2020-36218
The CVE-2020-36218 issue affects the Rust crate buttplug (versions before 1.0.4). The root cause is that ButtplugFutureStateShared does not properly respect types that are not Send or not Sync, allowing a data race on such objects. The vulnerability is documented across multiple sources (e.g., RU...
CVE-2020-36218
An issue was discovered in the buttplug crate before 1.0.4 for Rust. ButtplugFutureStateShared does not properly consider !Send|!Sync objects, leading to a data race...
CVE-2020-36219
The CVE-2020-36219 entry concerns the Rust crate atomic-option, where AtomicOption unconditionally implements Sync. This enables data races when non-Sync types are moved across threads, as reported in multiple sources (RustSec/RUSTSEC-2020-0113 and GHSA/RH updates). Affected component: atomic-opt...
CVE-2020-36219
An issue was discovered in the atomic-option crate through 2020-10-31 for Rust. Because AtomicOption implements Sync unconditionally, a data race can occur...
CVE-2020-36220
An issue was discovered in the va-ts crate before 0.0.4 for Rust. Because Demuxer omits a required T: Send bound, a data race and memory corruption can occur...
CVE-2020-36220
CVE-2020-36220 affects the Rust crate va-ts (before 0.0.4). TheDemuxer type omits a required T: Send bound, allowing non‑Send types to be carried across thread boundaries. This can lead to a data race and memory corruption. The issue is documented in multiple sources (including Red Hat and RustSe...
CVE-2021-25901
CVE-2021-25901 concerns the lazy-init crate for Rust, where the absence of a Send bound enables data races in safe code. Consequence is potential data contention and non-deterministic behavior if the crate is used in multi-threaded contexts. Public advisories (RustSec/RustSec-advisory style) desc...