Most recent entries from all

cnvd-2021-78756

2026-10-18T05:39:12.094148+00:00

cnvd-2021-78756

EUVD-2026-48184

2026-10-18T05:39:12.094187+00:00

EUVD-2026-48184

fkie_cve-2020-36439

2026-10-18T05:39:12.094212+00:00

An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket and WriteTicket.

GHSA-77m6-x95j-75r5 — Data races in ticketed_lock

2026-10-18T05:39:12.094242+00:00

Affected: crates.io: ticketed_lock

Affected versions of this crate unconditionally implemented Send for ReadTicket & WriteTicket. This allows to send non-Send T to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket/WriteTicket). Such data races can cause memory corruption or other undefined behavior. The flaw was corrected in commit `a986a93` by adding T: Send bounds to Send impls of ReadTicket/WriteTicket.

gsd-2020-36439

2026-10-18T05:39:12.094268+00:00

gsd-2020-36439

RUSTSEC-2020-0119 — ReadTicket and WriteTicket should only be sendable when T is Send

2026-10-18T05:39:12.094279+00:00

Affected: crates.io: ticketed_lock

Affected versions of this crate unconditionally implemented `Send` for `ReadTicket` & `WriteTicket`. This allows to send non-Send `T` to other threads.

This can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket`/`WriteTicket`). Such data races can cause memory corruption or other undefined behavior.

The flaw was corrected in commit a986a93 by adding `T: Send` bounds to `Send` impls of `ReadTicket`/`WriteTicket`.