Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-416 (释放后使用) — Vulnerability Class 2435

2435 vulnerabilities classified as CWE-416 (释放后使用). AI Chinese analysis included.

CWE-416, Use After Free, is a critical memory safety weakness occurring when a program continues to reference a memory location after it has been deallocated. Attackers typically exploit this vulnerability by freeing an object and then rapidly reallocating that same memory block with attacker-controlled data. Because the original pointer still points to the now-invalid address, the application may inadvertently execute malicious code or corrupt memory structures, often leading to arbitrary code execution or denial of service. To prevent this, developers must rigorously manage memory lifecycles by nullifying pointers immediately after freeing them, ensuring no dangling references remain. Utilizing modern programming languages with automatic garbage collection or employing static analysis tools to detect invalid memory accesses further mitigates the risk, ensuring that freed memory is never accessed again during the program’s execution.

MITRE CWE Description
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.
Common Consequences (4)
IntegrityModify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
AvailabilityDoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
ConfidentialityRead Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity, Confidentiality, AvailabilityExecute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap …
Mitigations (2)
Architecture and DesignChoose a language that provides automatic memory management.
ImplementationWhen freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Effectiveness: Defense in Depth
Examples (2)
The following example demonstrates the weakness.
#include <stdio.h> #include <unistd.h> #define BUFSIZER1 512 #define BUFSIZER2 ((BUFSIZER1/2) - 8) int main(int argc, char **argv) { char *buf1R1; char *buf2R1; char *buf2R2; char *buf3R2; buf1R1 = (char *) malloc(BUFSIZER1); buf2R1 = (char *) malloc(BUFSIZER1); free(buf2R1); buf2R2 = (char *) malloc(BUFSIZER2); buf3R2 = (char *) malloc(BUFSIZER2); strncpy(buf2R1, argv[1], BUFSIZER1-1); free(buf1R1); free(buf2R2); free(buf3R2); }
Bad · C
The following code illustrates a use after free error:
char* ptr = (char*)malloc (SIZE); if (err) { abrt = 1; free(ptr); } ... if (abrt) { logError("operation aborted before commit", ptr); }
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2026-7907 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-05-06
CVE-2026-7906 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-05-06
CVE-2026-7901 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-05-06
CVE-2026-7897 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-05-06
CVE-2026-7898 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-05-06
CVE-2026-23631 redis-server Lua use-after-free may allow remote code execution — redis 8.8 -2026-05-05
CVE-2026-23479 redis-server use-after-free in unblock client flow may allow remote code execution — redis 8.8 -2026-05-05
CVE-2026-24082 Use After Free in Automotive GPU — Snapdragon 7.8 High2026-05-04
CVE-2026-22166 GPU DDK - Write UAF in KEGLGetPoolBuffers, WebGL reachable — Graphics DDK 8.8 -2026-05-01
CVE-2026-22165 GPU DDK - UAF read of GLES3Context::psDrawParams and GLES3Context::psMode and UAF read/write of RMJob::apsCCBs — Graphics DDK 8.8 -2026-05-01
CVE-2026-5655 Use After Free in Wireshark — Wireshark 5.5 Medium2026-04-30
CVE-2026-7355 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7341 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7342 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7338 Google Chrome 资源管理错误漏洞 — Chrome 8.0AIHighAI2026-04-28
CVE-2026-7347 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7336 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7335 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7348 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7349 Google Chrome 资源管理错误漏洞 — Chrome 8.0AIHighAI2026-04-28
CVE-2026-7350 Google Chrome 资源管理错误漏洞 — Chrome 9.6AICriticalAI2026-04-28
CVE-2026-7352 Google Chrome 资源管理错误漏洞 — Chrome 9.6AICriticalAI2026-04-28
CVE-2026-7357 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7356 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7358 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7334 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28
CVE-2026-7359 Google Chrome 资源管理错误漏洞 — Chrome 9.6AICriticalAI2026-04-28
CVE-2026-7343 Google Chrome 资源管理错误漏洞 — Chrome 9.6AICriticalAI2026-04-28
CVE-2026-7333 Google Chrome 资源管理错误漏洞 — Chrome 9.6AICriticalAI2026-04-28
CVE-2026-7361 Google Chrome 资源管理错误漏洞 — Chrome 8.8AIHighAI2026-04-28

Vulnerabilities classified as CWE-416 (释放后使用) represent 2435 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.