The issue allows remote attackers to cause a denial of service and enable certain double-spending capabilities via a large block that triggers incorrect Berkeley DB locking, due to improper consideration of whether a block's size could require an excessive number of database locks.