LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32810: Data race in crossbeam-deque

crossbeam-deque is a package of work-stealing deques for building task schedulers when programming in Rust. In versions prior to 0.7.4 and 0.8.0, 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a serious bug in the Rust crossbeam-deque library. Under concurrent task-stealing, work items can be processed twice while others are silently skipped. For affected software, that can mean memory corruption, memory leaks, crashes, or incorrect business logic.

Executive priority

Treat as urgent for Rust-based production systems because the stated impact includes memory safety and task correctness failures. Prioritize inventory and dependency updates over emergency incident response unless local evidence shows crashes or anomalous task behavior.

Technical view

CVE-2021-32810 is a CWE-362 data race in crossbeam-deque affecting versions <0.7.4 and >=0.8.0,<0.8.1. Crates using Stealer::steal, steal_batch, or steal_batch_and_pop are affected. The race can duplicate popped tasks and lose others, potentially causing double free, memory leak, or logical failure.

Likely exposure

Exposure is most likely in Rust applications or packaged software that directly or transitively uses vulnerable crossbeam-deque versions, especially task schedulers or concurrent worker systems using the affected Stealer APIs.

Exploitation context

The source bundle does not identify active exploitation, and KEV is false. The CVSS vector rates this as network-reachable with low complexity and no privileges or user interaction, but the provided sources do not explain real-world exploitability conditions.

Researcher notes

The advisory clearly identifies affected APIs and fixed versions, but the bundle lacks proof-of-concept details, exploit sightings, or environmental prerequisites. Validation should focus on dependency reachability and whether vulnerable Stealer APIs are actually exercised.

Mitigation direction

  • Upgrade crossbeam-deque to 0.8.1 or 0.7.4.
  • Regenerate dependency locks after upgrading Rust crates.
  • Review vendor or distribution advisories for packaged Fedora software.
  • Prioritize services using concurrent task scheduling or work stealing.
  • Check vendor guidance if crossbeam is embedded in third-party products.

Validation and detection

  • Inspect Cargo.lock for crossbeam-deque versions in affected ranges.
  • Identify code paths using Stealer::steal, steal_batch, or steal_batch_and_pop.
  • Run dependency audit tooling against Rust manifests and lockfiles.
  • Confirm rebuilt artifacts include crossbeam-deque 0.8.1 or 0.7.4.
  • Review runtime incidents for unexplained task loss, duplicate execution, or crashes.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32810 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
16Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-32810Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
crossbeam-rscrossbeam< 0.7.4, >= 0.8.0, < 0.8.1Listed
Weakness

CWE details

CWE-362

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs