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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

4332 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-113205 Chrome 156.0.8078.47 之前 Variations 远程代码执行漏洞 — Chrome - - 2026-10-20
CVE-2026-113290 Chrome 156.0.8078.47 前 Input 组件 Use-After-Free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113155 Chrome 156.0.8078.47 之前 Glic 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113108 Chrome 156 前 Script 组件存在释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113319 Chrome 156 之前版本无障碍功能存在释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113105 Chrome 156.0.8078.47 前扩展 Use-After-Free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113014 Chrome 156 前 PerformanceAPIs 远程代码执行漏洞 — Chrome - - 2026-10-20
CVE-2026-113275 Chrome 156 之前版本 API 中存在释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113302 Chrome 156.0.8078.47 扩展 Use-After-Free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113311 Chrome 156.0.8078.47 之前 ServiceWorker 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113033 Chrome 156 之前 Streaming 组件存在释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113011 Chrome 156.0.8078.47 之前版本 CredentialProvider 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113198 Chrome 156 之前扩展功能 Use-after-free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113240 Chrome 156 前版本 Chromecast 存在释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113263 Chrome 156 前 Android 版 Core 组件存在远程代码执行漏洞 — Chrome - - 2026-10-20
CVE-2026-113113 Chrome 156.0.8078.47 前扩展 Use-after-free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113250 Chrome 156.0.8078.47 前 ANGLE 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113079 Chrome 156.0.8078.47 前 SiteIsolation 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113191 Chrome 156 之前版本 Internals 存在 UAF 漏洞 — Chrome - - 2026-10-20
CVE-2026-113174 Chrome 156 扩展 Use-After-Free 远程代码执行漏洞 — Chrome - - 2026-10-20
CVE-2026-112993 Chrome 156.0.8078.47 前 Input 组件 Use-after-free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113068 Chrome 156.0.8078.47 前 Input 模块释放后重用漏洞 — Chrome - - 2026-10-20
CVE-2026-113179 Chrome 156.0.8078.47 前 Paint 用后释漏洞 — Chrome - - 2026-10-20
CVE-2026-113181 Chrome 156 导航模块 Use-after-free 漏洞 — Chrome - - 2026-10-20
CVE-2026-113160 Chrome 156.0.8078.47 前 Turbolev 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113019 Chrome 156.0.8078.47 前 Turbolev 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113161 Chrome 156 前 WebRTC 远程代码执行漏洞 — Chrome - - 2026-10-20
CVE-2026-113217 Chrome Android 156.0.8078.47 前 WebAppInstalls 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113222 Chrome 156.0.8078.47 前 V8 释放后使用漏洞 — Chrome - - 2026-10-20
CVE-2026-113338 Chrome 156.0.8078.47 前 Turbolev 远程代码执行漏洞 — Chrome - - 2026-10-20

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