Deps.rs

crossbeam 0.5.0

[![dependency status](https://deps.rs/crate/crossbeam/0.5.0/status.svg)](https://deps.rs/crate/crossbeam/0.5.0)

This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate crossbeam

Dependencies

(8 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^0.11.0.0out of date
 crossbeam-channel^0.30.5.12out of date
 crossbeam-deque ⚠️^0.60.8.5out of date
 crossbeam-epoch^0.60.9.18out of date
 crossbeam-utils^0.60.8.19out of date
 lazy_static^1.1.01.4.0up to date
 num_cpus^1.8.01.16.0up to date
 parking_lot^0.6.40.12.1out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 rand^0.50.8.5out of date

Security Vulnerabilities

crossbeam-deque: Data race in crossbeam-deque

RUSTSEC-2021-0093

In the affected version of this crate, the result of the race condition is that one or more tasks in the worker queue can be popped twice instead of other tasks that are forgotten and never popped. If tasks are allocated on the heap, this can cause double free and a memory leak. If not, this still can cause a logical bug.

Crates using Stealer::steal, Stealer::steal_batch, or Stealer::steal_batch_and_pop are affected by this issue.

Credits to @kmaork for discovering, reporting and fixing the bug.