CWE-416: Use After Free
VariantStableExploit Likelihood: High🏆 #16 in Top 25 (2024)
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
View on MITRE1,151Related CVEs
12.89Severity Score
Back to CWE Lookup
Technical Details
- Structure
- Simple
Applicable To
CC++
🏆 CWE Top 25 Historical Ranking
2023:#4
Score: 16.71
1,172 CVEs
2024:#16↓12
Score: 12.89
1,151 CVEs
Trend:Improving (moved up 12 ranks)
Learn More
Find Related CVEs
Search for vulnerabilities that exploit CWE-416
CWE Top 25 Most Dangerous
See how this weakness ranks against others
CVE vs CWE: What's the Difference?
Understanding vulnerabilities vs weaknesses
Understanding CVSS Scoring
How vulnerability severity is measured
View Full MITRE Entry
Complete technical details and references