CWE•Base•Draft•15 recent CVEs
CWE-413Improper Resource Locking
Description
The product must have exclusive access to a resource, but it does not lock or does not correctly lock that resource.
Common consequences
- Integrity,Availability→Modify Application Data,DoS: Instability,DoS: Crash, Exit, or RestartWhen a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected beh
Potential mitigations
- Architecture and DesignUse a non-conflicting privilege scheme.
- Architecture and Design,ImplementationUse synchronization when locking a resource.
Related CWEs
Recent CVEs classified under this CWE
CVE-2026-407052026-11-10CVE-2026-481788.82026-11-05CVE-2026-1114984.72026-10-30CVE-2026-1020835.92026-10-14CVE-2026-1020805.32026-10-14CVE-2026-1053902026-10-13CVE-2026-926156.62026-09-16CVE-2026-446085.92026-05-20CVE-2026-327487.52026-03-26CVE-2025-00037.32025-11-24CVE-2025-345010.02025-10-07CVE-2023-322535.92025-08-02CVE-2023-339516.72023-07-24CVE-2023-22694.42023-04-25CVE-2022-249467.52022-06-15