What is CVE-2021-32810?

CVE-2021-32810 is a critical-severity race condition vulnerability in crossbeam-deque (rust), affecting versions < 0.7.4. It is fixed in 0.7.4, 0.8.1. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

How severe is CVE-2021-32810?

CVE-2021-32810 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of crossbeam-deque are affected by CVE-2021-32810?

crossbeam-deque (rust) versions < 0.7.4 is affected.

Is there a fix for CVE-2021-32810?

Yes. CVE-2021-32810 is fixed in 0.7.4, 0.8.1. Upgrade to this version or later.

Is CVE-2021-32810 exploitable, and should I be worried?

Whether CVE-2021-32810 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2021-32810 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2021-32810?

Upgrade: crossbeam-deque to 0.7.4 or later, crossbeam-deque to 0.8.1 or later.

CVE-2021-32810 in crossbeam-deque

Q: How severe is CVE-2021-32810?

CVE-2021-32810 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of crossbeam-deque are affected by CVE-2021-32810?

crossbeam-deque (rust) versions < 0.7.4 is affected.

Q: Is there a fix for CVE-2021-32810?

Yes. CVE-2021-32810 is fixed in 0.7.4, 0.8.1. Upgrade to this version or later.

Q: Is CVE-2021-32810 exploitable, and should I be worried?

Whether CVE-2021-32810 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2021-32810 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2021-32810?

Upgrade: crossbeam-deque to 0.7.4 or later, crossbeam-deque to 0.8.1 or later.

Summary

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

Credits

This issue was reported and fixed by Maor Kleinberger.

License

This advisory is in the public domain.

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.

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2021-32810 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.7.4, 0.8.1); upgrading removes the vulnerable code path.

Affected versions

crossbeam-deque (< 0.7.4) crossbeam-deque (>= 0.8.0, < 0.8.1)

Security releases

crossbeam-deque → 0.7.4 (rust) crossbeam-deque → 0.8.1 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This has been fixed in crossbeam-deque 0.8.1 and 0.7.4.

Frequently Asked Questions

What is CVE-2021-32810? CVE-2021-32810 is a critical-severity race condition vulnerability in crossbeam-deque (rust), affecting versions < 0.7.4. It is fixed in 0.7.4, 0.8.1. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
How severe is CVE-2021-32810? CVE-2021-32810 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of crossbeam-deque are affected by CVE-2021-32810? crossbeam-deque (rust) versions < 0.7.4 is affected.
Is there a fix for CVE-2021-32810? Yes. CVE-2021-32810 is fixed in 0.7.4, 0.8.1. Upgrade to this version or later.
Is CVE-2021-32810 exploitable, and should I be worried? Whether CVE-2021-32810 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2021-32810 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2021-32810?
- Upgrade crossbeam-deque to 0.7.4 or later
- Upgrade crossbeam-deque to 0.8.1 or later