CWE-832 Unlock of a Resource that is not Locked

The product attempts to unlock a resource that is not locked.

• Integrity, Confidentiality, Availability, Other: DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands, Modify Memory, Other — Depending on the locking functionality, an unlock of a non-locked resource might corrupt the state of the product, possibly including denial of service, memory corruption, or other modification to the resource (or its associated metadata that is used for tracking locks). In some cases, an unlock operation might not have any adverse effects.

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

• CVE-2010-4210: function in OS kernel unlocks a mutex that was not previously locked, causing a panic or overwrite of arbitrary memory. • CVE-2008-4302: Chain: OS kernel does not properly handle a failure of a function call (CWE-755), leading to an unlock of a resource that was not locked (CWE-832), with resultant crash. • CVE-2009-1243: OS kernel performs an unlock in some incorrect circumstances, leading to panic.