CVE-2020-35905

An issue was discovered in the futures-util crate before 0.3.7 for Rust. MutexGuard::map can cause a data race for certain closure situations in safe code...

CVE-2020-35905

The CVE-2020-35905 issue affects the futures-util crate for Rust (pre-0.3.7). A MutexGuard::map path can cause a data race in safe code under certain closure scenarios. This is a local issue in the crate’s synchronization logic that could lead to data races, as described in the advisory and Red H...

CVE-2020-35910

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness...

CVE-2020-35910

CVE-2020-35910 affects the Rust crate lock_api prior to version 0.4.2. The issue is a data race caused by unsoundness in MappedMutexGuard, as reported across multiple sources referencing the same flaw in lock_api. This can enable data races in affected code paths that rely on the lock. The vulner...

CVE-2020-35910

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness...

CVE-2020-35911

CVE-2020-35911 affects the Rust lock_api crate prior to 0.4.2. The issue is a data race caused by unsoundness in MappedRwLockReadGuard, with no explicit exploit details provided. Remediation: upgrade to 0.4.2 or later. Details are limited to the provided documents.

CVE-2020-35911

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness...

CVE-2020-35911

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness...

CVE-2020-35912

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness...

CVE-2020-35912

CVE-2020-35912 affects the Rust lock_api crate prior to 0.4.2, where a data race can occur due to unsoundness in MappedRwLockWriteGuard. The connected records corroborate the vulnerability text but do not provide explicit exploitation details, affected products beyond the Rust crate, or a stated ...

CVE-2020-35912

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness...

CVE-2020-35913

CVE-2020-35913 concerns the Rust crate lock_api (pre-0.4.2). The issue is a data race caused by unsoundness in RwLockReadGuard , as documented across multiple sources in the connected set (e.g., Red Hat advisory and OSV entries). Affected component: the lock_api crate before version 0.4.2. Impact...

CVE-2020-35913

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness...

CVE-2020-35913

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness...

CVE-2020-35914

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness...

CVE-2020-35914

The CVE-2020-35914 issue affects the Rust lock_api crate, specifically versions before 0.4.2. The root cause is a data race caused by unsoundness in RwLockWriteGuard. Impact is described as a data race condition; exploitation details are not provided in the supplied documents. Public references (...

CVE-2020-35914

An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness...

CVE-2020-35928

Concread crate (Rust) before 0.2.6 exposes a data race in ARCache when non-Send/Sync types are used. Root cause: ARCache implementation unbound by Send/Sync, allowing unsafe concurrent access. The issue was fixed in 0.2.6 by adding K: Send + Sync and V: Send + Sync bounds to the affected Send/Syn...

CVE-2020-35928

An issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache data race by sending types that do not implement Send/Sync...

RUSTSEC-2020-0143 Queues allow non-Send types to be sent to other threads, allowing data races

Affected versions of this crate unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior...