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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

3813 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)
Integrity Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability DoS: 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.
Confidentiality Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity, Confidentiality, Availability Execute 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 Design Choose a language that provides automatic memory management.
Implementation When 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 ID Title CVSS Severity Published
CVE-2026-106269 Chrome <155.0.8059.39 CSS释放后使用远程代码执行 — Chrome - - 2026-10-06
CVE-2026-106234 Chrome 155.0.8059.39前扩展Use After Free漏洞 — Chrome - - 2026-10-06
CVE-2026-106373 Google Chrome Fonts使用释放后漏洞 — Chrome - - 2026-10-06
CVE-2026-106335 Chrome < 155.0.8059.39 Media Use-After-Free 远程代码执行 — Chrome - - 2026-10-06
CVE-2026-106291 Chrome 155.0.8059.39前版本UAF漏洞可导致远程代码执行 — Chrome - - 2026-10-06
CVE-2026-106283 Google Chrome <155.0.8059.39 流媒体组件UAF漏洞 — Chrome - - 2026-10-06
CVE-2026-106315 Chrome<155.0.8059.39模块化UAF漏洞 — Chrome - - 2026-10-06
CVE-2026-106200 Google Chrome <155.0.8059.39 越界释放漏洞 — Chrome - - 2026-10-06
CVE-2026-106204 Chrome <155.0.8059.39 PDF使用释放后漏洞 — Chrome - - 2026-10-06
CVE-2026-106421 Chrome<155.0.8059.39 PDF内存释放后使用漏洞 — Chrome - - 2026-10-06
CVE-2026-106357 Chrome 155.0.8059.39前版本WebRTC Use-After-Free漏洞 — Chrome - - 2026-10-06
CVE-2026-106190 Chrome <155.0.8059.39 媒体组件Use after free漏洞 — Chrome - - 2026-10-06
CVE-2026-106383 Chrome <155.0.8059.39 Media使用释放后漏洞 — Chrome - - 2026-10-06
CVE-2026-106349 Chrome <155.0.8059.39 V8 UAF漏洞 — Chrome - - 2026-10-06
CVE-2026-106278 Chrome<155.0.8059.39 Select使用释放后漏洞 — Chrome - - 2026-10-06
CVE-2026-106233 Chrome<155.0.8059.39使用之后释放漏洞 — Chrome - - 2026-10-06
CVE-2026-106411 Chrome <155.0.8059.39 解析器Use After Free漏洞 — Chrome - - 2026-10-06
CVE-2026-106318 Chrome 155.0.8059.39前媒体模块use-after-free漏洞 — Chrome - - 2026-10-06
CVE-2026-106423 Chrome <155.0.8059.39媒体模块UAF漏洞 — Chrome - - 2026-10-06
CVE-2026-106268 Chrome < 155.0.8059.39 WebRTC 释放后使用漏洞 — Chrome - - 2026-10-06
CVE-2026-106257 Chrome <155.0.8059.39 HTML Use-After-Free远程代码执行漏洞 — Chrome - - 2026-10-06
CVE-2026-106211 Chrome低于155.0.8059.39 TabStrip堆后使用漏洞 — Chrome - - 2026-10-06
CVE-2026-106235 Google Chrome 155.0.8059.39前远程代码执行漏洞 — Chrome - - 2026-10-06
CVE-2026-106248 Chrome <155.0.8059.39 远程代码执行漏洞 — Chrome - - 2026-10-06
CVE-2026-106193 Chrome<155.0.8059.39任意代码执行漏洞 — Chrome - - 2026-10-06
CVE-2026-106393 Chrome小于155.0.8059.39存储模块UAF漏洞 — Chrome - - 2026-10-06
CVE-2026-106298 Chrome < 155.0.8059.39 Mac 使用-after-free漏洞 — Chrome - - 2026-10-06
CVE-2026-106227 Chrome < 155.0.8059.39内核堆后释放漏洞 — Chrome - - 2026-10-06
CVE-2026-106281 Google Chrome 155.0.8059.39 前 Tint UAF 漏洞 — Chrome - - 2026-10-06
CVE-2026-106419 Chrome <155.0.8059.39 堆释放后使用致代码执行 — Chrome - - 2026-10-06

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