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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

3304 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-43632 llama.cpp b7492–b9060 Use-After-Free in Tokenization Endpoints — llama.cpp 8.1 High2026-08-06
CVE-2026-43631 llama.cpp b7492–b9060 Use-After-Free RCE via llama-server — llama.cpp 8.1 High2026-08-06
CVE-2026-71226 Libkcapi: memory corruption via uncanceled aio requests on error in libkcapi's one-shot aio path — libkcapi 7.3 High2026-08-05
CVE-2026-18785 o6 open62541 client_types_custom.c UA_Client_getRemoteDataTypes use after free — open62541 5.3 Medium2026-08-04
CVE-2026-56848 Node.js 资源管理错误漏洞 — node--2026-08-04
CVE-2026-11368 Use-after-free in Bluetooth host ATT TX completion on disconnect mid-transfer — zephyr 7.1 High2026-08-04
CVE-2026-62870 Microsoft Excel Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 8.8 High2026-08-03
CVE-2026-66315 Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability — Microsoft Edge (Chromium-based) 7.5 High2026-08-03
CVE-2026-20473 MediaTek Chipsets 资源管理错误漏洞 — MediaTek chipset--2026-08-03
CVE-2026-67299 FreeRDP before 3.29.0 Use-After-Free via WindowIcon async message — FreeRDP 7.5 High2026-08-01
CVE-2026-67300 FreeRDP before 3.29.0 Use-After-Free via async message proxy — FreeRDP 7.5 High2026-08-01
CVE-2026-10685 Use-after-free of GATT subscribe params in Bluetooth host CCC-write response handler — zephyr 7.6 High2026-07-31
CVE-2026-63035 o6 Automation open62541 Use After Free — open62541 8.1 High2026-07-30
CVE-2026-12996 OpenVPN 缓冲区错误漏洞 — OpenVPN 6.0 Medium2026-07-30
CVE-2026-54522 MessagePack::Buffer#clear Use-After-Free that Enables Cross-Buffer Disclosure — msgpack-ruby 2.1 Low2026-07-30
CVE-2026-13117 OpenVPN 资源管理错误漏洞 — OpenVPN 6.0 Medium2026-07-30
CVE-2026-18017 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-18012 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17967 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17947 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17932 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17924 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17920 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17918 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17898 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17894 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17896 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17891 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17887 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30
CVE-2026-17886 Google Chrome 资源管理错误漏洞 — Chrome--2026-07-30

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