Use-after-free
Named by 32 kept items in this workspace.
17 items name it under classification.key entities and 15 under techniques.
Search every workspace for Use-after-free. It matches the name as written, so it can find other things that share it.
The items that name it 32
CVE-2026-98432 is a use-after-free in the kernel's IPv4 TCP code: tcp_v4_syn_recv_sock() transfers ireq->ireq_opt to the child socket without copying it.
The flaw: IPv4 options object ireq_opt/inet_opt is freed with kfree() while another CPU still reads it as an RCU reader.
PHP2Shell forces PHP out of memory mid-request, leaving a dangling pointer to freed memory that the next request fills with crafted data, read as an internal object.
Flaw in ip_options_build(): the child socket's inet_opt is freed with a plain kfree() while another CPU still builds a SYNACK from ireq->ireq_opt
Vulnerability class in curl's HTTP/2 upload handling that turned into RCE, described by Daniel Stenberg.
125 issues fixed in Chrome 156
The V8 sandbox escape (issue 546253900) causes a worker's native V8 isolate pointer to be freed while a backing store (A) still references it, enabling a native use-after-free reached via memory.grow(0)
Class of all four critical-severity flaws fixed in the Chrome 155 update (CVE-2026-106382, CVE-2026-106197, CVE-2026-106358, CVE-2026-106347); 34 use-after-free bugs were fixed in total.
Vulnerability class left unaddressed by patches judged 'clean' by Chromium's automated grader in 1Password's benchmark; also the root cause pattern in the freenginx bug where a callback could be used after being destroyed by Perl
program continues using a pointer after the memory it points to has been deallocated, creating a dangling pointer that can corrupt or control reassigned memory; related to double free
Potential use after free
ngx_http_ssi_module
All techniques in this workspace.