use-after-free

Use-after-free is a memory safety vulnerability in which a program continues to reference memory after it has been freed, which can be exploited for remote code execution.

1 articleLast mentioned

Use-after-free (UAF) is a memory safety vulnerability that occurs when a program continues to use a pointer to dynamically allocated memory after that memory has been freed. If the freed region is reallocated for other data, the program may read or write corrupted values, leading to crashes, information disclosure, or arbitrary code execution. It is classified as CWE-416 in the Common Weakness Enumeration.

The bug arises mainly in languages such as C and C++ where programmers manage memory manually, and a large share of the critical vulnerabilities found in web browsers, operating system kernels, and language interpreters are of this type. It is one of the main motivations behind the move toward memory-safe languages such as Rust.

This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.

Articles covering this entry

  • Nine AI Platforms Breached in a Month: Old Bugs at Machine Speed and Five FixesAI Security ·

    It is a use-after-free memory corruption bug: when the interpreter hits a fatal out-of-memory error, it fails to clean up properly and leaves corrupted memory t…

    Read article

Found a mistake or missing an entry?

Wiki entries are based on AIPOST articles and widely known facts. If an entry is wrong, send us a correction request and we will check and fix it. Names from new articles are added to the wiki after the article is published.