CVE-2021-32810Critical· 9.8▾ Midnightcrossbeam-deque Data Race before v0.7.4 and v0.8.1
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.4 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 9.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.9%
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.
This has been fixed in crossbeam-deque 0.8.1 and 0.7.4.
This issue was reported and fixed by Maor Kleinberger.
This advisory is in the public domain.
crossbeam-deque < 0.7.4crossbeam-deque >= 0.8.0, < 0.8.1Upgrade to a patched release:
crossbeam-deque 0.7.4crossbeam-deque 0.8.1