Most recent entries from all

EUVD-2026-47906

2026-10-16T18:41:27.147465+00:00

EUVD-2026-47906

fkie_cve-2020-35914

2026-10-16T18:41:27.147510+00:00

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

GHSA-gmv4-vmx3-x9f3 — Data races in lock_api

2026-10-16T18:41:27.147555+00:00

Affected: crates.io: lock_api

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

gsd-2020-35914

2026-10-16T18:41:27.147603+00:00

gsd-2020-35914

RUSTSEC-2020-0070 — Some lock_api lock guard objects can cause data races

2026-10-16T18:41:27.147627+00:00

Affected: crates.io: lock_api

Affected versions of lock_api had unsound implementations of the `Send` or `Sync` traits for some guard objects, namely:

* MappedMutexGuard * MappedRwLockReadGuard * MappedRwLockWriteGuard * RwLockReadGuard * RwLockWriteGuard

These guards could allow data races through types that are not safe to `Send` across thread boundaries in safe Rust code.

This issue was fixed by changing the trait bounds on the `Mapped` guard types and removing the `Sync` trait for the `RwLock` guards.

UBUNTU-CVE-2020-35914

2026-10-16T18:41:27.147677+00:00

Affected: Ubuntu:20.04:LTS: rust-lock-api, Ubuntu:22.04:LTS: rust-lock-api, Ubuntu:24.04:LTS: rust-lock-api, Ubuntu:25.10: rust-lock-api, Ubuntu:26.04:LTS: rust-lock-api

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