The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.
View on MITREEach thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.
No mitigation information available for this CWE.
No detection method information available for this CWE.
A bug in some Intel Pentium processors allow DoS (hang) via an invalid "CMPXCHG8B" instruction, causing a deadlock
View Detailschain: other weakness leads to NULL pointer dereference (CWE-476) or deadlock (CWE-833).
View Detailsdeadlock when an operation is performed on a resource while it is being removed.
View DetailsDeadlock in device driver triggered by using file handle of a related device.
View DetailsDeadlock when large number of small messages cannot be processed quickly enough.
View DetailsAdditional facts reviewed against primary or authoritative security sources.
Documented detection approaches include Automated Static Analysis; recorded impacts include DoS: Resource Consumption (CPU), DoS: Resource Consumption (Other), and DoS: Crash, Exit, or Restart; the entry maps to CAPEC-25. Use these source-defined anchors to turn CWE-833 into implementation, review, and verification checks for the affected component.
CWE-833: Deadlock — MITRE CWEUse NIST SSDF practices to make prevention of CWE-833, Deadlock, an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.
NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and TechnologyUse CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-833, Deadlock, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.
Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security AgencyApply MITRE's full root-cause mapping guidance when using CWE-833, Deadlock. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.
CVE to CWE Root Cause Mapping Guidance — MITRE CWEApply MITRE's root-cause mapping quick tips to CWE-833, Deadlock. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.
CVE to CWE Root Cause Mapping Quick Tips — MITRE CWECWE-833: Deadlock is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.
If exploited, CWE-833 (Deadlock) it can compromise Availability, leading to outcomes such as DoS: Resource Consumption (CPU), DoS: Resource Consumption (Other) and DoS: Crash, Exit, or Restart.
CWE-833 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
MITRE documents real CVEs mapped to CWE-833, including CVE-1999-1476, CVE-2009-2857, CVE-2009-1961, CVE-2009-2699 and CVE-2009-4272. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-833 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.