Use-after-free vulnerabilities remain difficult to detect and mitigate, making them a popular
source of exploitation. Existing solutions incur impractical performance/memory overhead …

Kernel memory allocators maintain several metadata structures optimized for efficiently
managing system memory. However, existing implementations adopt either weak or no …

Spatial memory errors such as buffer overflows still rank among the top vulnerabilities in
C/C++ programs. Despite much research in the area, the performance overhead of (even …

Memory tagging allows to establish memory safety for software developed in unsafe
languages like C/C++. Since it is an effective mechanism with low architectural complexity …

Low-level languages, which require manual memory management from the programmer,
remain in wide use for performance-critical applications. Memory-safety bugs are common …

Information leakage vulnerabilities (or simply info leaks) such as out-of-bounds/uninitialized
reads in the architectural or speculative domain pose a significant security threat, allowing …

Use-after-free (UAF) is a critical and prevalent problem in memory unsafe languages. While
many solutions have been proposed, balancing security, run-time cost, and memory …

Critical software is written in memory unsafe languages that are vulnerable to use-after-free
and double free bugs. This has led to proposals to secure memory allocators by strategically …

Memory-safety issues in operating systems and popular applications are still top security
threats. As one widely exploited vulnerability, Use After Free (UAF) resulted in hundreds of …

The widespread deployment of control-flow integrity has propelled non-control data attacks
into the mainstream. In the domain of OS kernel exploits, by corrupting critical non-control …