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 DetailsCWE-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.
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.