Resource Locking Problems
A category in the Common Weakness Enumeration published by The MITRE Corporation.
Summary
Categories in the Common Weakness Enumeration (CWE) group entries based on some common characteristic or attribute.
Weaknesses in this category are related to improper handling of locks that are used to control access to resources.
Weaknesses
The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.
The product uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.
The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.
A product does not check to see if a lock is present before performing sensitive operations on a resource.
The product locks a critical resource more times than intended, leading to an unexpected state in the system.
The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.
The product attempts to unlock a resource that is not locked.
The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of ...
Concepts
This view organizes weaknesses around concepts that are frequently used or encountered in software development. This includes all aspects of the software development l...
Common Weakness Enumeration content on this website is copyright of The MITRE Corporation unless otherwise specified. Use of the Common Weakness Enumeration and the associated references on this website are subject to the Terms of Use as specified by The MITRE Corporation.