https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 18:58:12 +0000 https://cve.radiocsirt.org/vuln/cve-2020-35910 <p>An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.</p> <p>An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.</p> https://cve.radiocsirt.org/vuln/cve-2020-35910 https://cve.radiocsirt.org/vuln/rustsec-2020-0070 <p><strong>Affected:</strong> crates.io: lock_api</p> <p>Affected versions of lock_api had unsound implementations of the `Send` or `Sync` traits for some guard objects, namely:</p> <p>* MappedMutexGuard * MappedRwLockReadGuard * MappedRwLockWriteGuard * RwLockReadGuard * RwLockWriteGuard</p> <p>These guards could allow data races through types that are not safe to `Send` across thread boundaries in safe Rust code.</p> <p>This issue was fixed by changing the trait bounds on the `Mapped` guard types and removing the `Sync` trait for the `RwLock` guards.</p> <p><strong>Affected:</strong> crates.io: lock_api</p> <p>Affected versions of lock_api had unsound implementations of the `Send` or `Sync` traits for some guard objects, namely:</p> <p>* MappedMutexGuard * MappedRwLockReadGuard * MappedRwLockWriteGuard * RwLockReadGuard * RwLockWriteGuard</p> <p>These guards could allow data races through types that are not safe to `Send` across thread boundaries in safe Rust code.</p> <p>This issue was fixed by changing the trait bounds on the `Mapped` guard types and removing the `Sync` trait for the `RwLock` guards.</p> https://cve.radiocsirt.org/vuln/rustsec-2020-0070