VariantDraft
CWE-401Missing Release of Memory after Effective Lifetime
Category: memory
Description
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Common consequences· 2
- Availability — DoS: Crash, Exit, or Restart, DoS: Instability, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory)Most memory leaks result in general product reliability problems, but if an attacker can intentionally trigger a memory leak, the attacker might be able to launch a denial of service attack (by crashing or hanging the program) or take advantage of other unexpected program behavior resulting from a low memory condition.
- Other — Reduce Performance
Potential mitigations· 3
- [Implementation]
- [Architecture and Design]Use an abstraction library to abstract away risky APIs. Not a complete solution.
- [Architecture and Design, Build and Compilation]Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
References
(incoming)5
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2025-20133cve-2025-20133 | 0% | live |
| Vulnerability | CVE-2025-20239cve-2025-20239 | 0% | live |
| Vulnerability | CVE-2025-29828cve-2025-29828 | 0% | live |
| Vulnerability | CVE-2026-20012cve-2026-20012 | 0% | live |
| KEVEntry | Arm Mali GPU Kernel Driver Information Disclosure Vulnerabilitykev-cve-2023-26083 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.