Annotation use-after-free exploitation pattern

Modern Adobe Reader exploits corrupt memory by spraying annotation objects with addAnnot(), freeing one with .destroy(), then re-entering through a getAnnot()/getAnnots() callback installed via Object.defineProperties (often with an annotation named 'uaf' and an Int32Array/ArrayBuffer info-leak). This is the reusable use-after-free shape behind several Reader annotation CVEs, so it is surfaced as a memory-corruption pattern rather than pinned to one CVE; the exact CVE depends on the targeted Reader build.