CWE-833: Deadlock

Description

The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.

N/A

Threat Mapped score: 0.0

Industry: Finiancial

Threat priority: Unclassified

CVE: CVE-1999-1476

A bug in some Intel Pentium processors allow DoS (hang) via an invalid "CMPXCHG8B" instruction, causing a deadlock
CVE: CVE-2009-2857

OS deadlock
CVE: CVE-2009-1961

OS deadlock involving 3 separate functions
CVE: CVE-2009-2699

deadlock in library
CVE: CVE-2009-4272

deadlock triggered by packets that force collisions in a routing table
CVE: CVE-2002-1850

read/write deadlock between web server and script
CVE: CVE-2004-0174

web server deadlock involving multiple listening connections
CVE: CVE-2009-1388

multiple simultaneous calls to the same function trigger deadlock.
CVE: CVE-2006-5158

chain: other weakness leads to NULL pointer dereference (CWE-476) or deadlock (CWE-833).
CVE: CVE-2006-4342

deadlock when an operation is performed on a resource while it is being removed.
CVE: CVE-2006-2374

Deadlock in device driver triggered by using file handle of a related device.
CVE: CVE-2006-2275

Deadlock when large number of small messages cannot be processed quickly enough.
CVE: CVE-2005-3847

OS kernel has deadlock triggered by a signal during a core dump.
CVE: CVE-2005-3106

Race condition leads to deadlock.
CVE: CVE-2005-2456

Chain: array index error (CWE-129) leads to deadlock (CWE-833)

Phase	Note
None listed.

Impact: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Other), DoS: Crash, Exit, or Restart — Notes: Each 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.

N/A