crossbeam-deque
Affected
- introduced
0, fixed0.7.4(semver)
Fixed versions
0.7.4
Fix
- Fixed version
0.7.4cargo update -p crossbeam-deque --precise 0.7.4
Advisory
Also known as: CVE-2021-32810, RUSTSEC-2021-0093
crossbeam-deque Data Race before v0.7.4 and v0.8.1
Impact
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.
Patches
This has been fixed in crossbeam-deque 0.8.1 and 0.7.4.
Credits
This issue was reported and fixed by Maor Kleinberger.
License
This advisory is in the public domain.
Critical Basis: The source's own band: CRITICAL
0, fixed 0.7.4 (semver)0.7.4
0.7.4cargo update -p crossbeam-deque --precise 0.7.40.8.0, fixed 0.8.1 (semver)0.8.1
0.8.1cargo update -p crossbeam-deque --precise 0.8.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0