Skip to content

crossbeam-deque Data Race before v0.7.4 and v0.8.1

Critical severity GitHub Reviewed Published Aug 2, 2021 in crossbeam-rs/crossbeam • Updated Jan 29, 2023

Package

cargo crossbeam-deque (Rust)

Affected versions

< 0.7.4
>= 0.8.0, < 0.8.1

Patched versions

0.7.4
0.8.1

Description

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.

References

@taiki-e taiki-e published to crossbeam-rs/crossbeam Aug 2, 2021
Published by the National Vulnerability Database Aug 2, 2021
Reviewed Aug 2, 2021
Published to the GitHub Advisory Database Aug 25, 2021
Last updated Jan 29, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

1.152%
(85th percentile)

Weaknesses

CVE ID

CVE-2021-32810

GHSA ID

GHSA-pqqp-xmhj-wgcw

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.