The software locks a critical resource more times than
					intended, leading to an unexpected state in the system. When software is operating in a concurrent environment and repeatedly
						locks a critical resource, the consequences will vary based on the type of
						lock, the lock's implementation, and the resource being protected. In some
						situations such as with semaphores, the resources are pooled and extra
						locking calls will reduce the size of the total available pool, possibly
						leading to degraded performance or a denial of service. If this can be
						triggered by an attacker, it will be similar to an unrestricted lock
						(CWE-412). In the context of a binary lock, it is likely that any duplicate
						locking attempts will never succeed since the lock is already held and
						progress may not be possible.