CWE-832: Unlock of a Resource that is not Locked
The product attempts to unlock a resource that is not locked.
Last updated
Overview
Depending on the locking functionality, an unlock of a non-locked resource might cause memory corruption or other modification to the resource (or its associated metadata that is used for tracking locks).
Real-world CVEs
1 recorded CVEs are caused by CWE-832 (Unlock of a Resource that is not Locked). The highest-severity and most recent are shown first.
Common consequences
What can happen when CWE-832 is exploited.
DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands, Modify Memory, Other
Affects: Integrity, Confidentiality, Availability, Other
Depending on the locking being used, an unlock operation might not have any adverse effects. When effects exist, the most common consequence will be a corruption of the state of the product, possibly leading to a crash or exit; depending on the implementation of the unlocking, memory corruption or code execution could occur.
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.