Use-After-Free Landscape: Temporal vs Spatial, kCFI, and the Proven-by-Construction Story
The 2024-2026 industry picture on temporal memory safety, kernel mitigations, and the convergence of UAF defences.
11 notes
The 2024-2026 industry picture on temporal memory safety, kernel mitigations, and the convergence of UAF defences.
Stenberg's curl CVE data, the Hyper / Rust experiment, and the unresolved 2026 question of whether memory-safe languages are the whole answer.
Chrome Security's published per-quarter memory-safety data for 2024-2026, the JSON / PNG / fonts Rust rollouts, and the V8 sandbox.
The CRA's 2026-2027 enforcement timeline and the implicit pressure toward memory-safe languages.
The DoD's evolving acquisition posture on memory-safe languages, the SWFT framework, and aerospace coding standards.
The White House Office of the National Cyber Director's memory-safety report and the C/C++-adverse federal stance.
The NSA's formal language-level guidance, the named-language list, and the joint CISA reissue.
The voluntary US federal pledge that has set the de-facto industry baseline for memory-safety roadmaps.
Google's published 2022-2026 data on memory-safety progress — Android's 76% → <20% trajectory, the CVE-2025-48530 near-miss, the V8 sandbox.
The canonical industry data point on memory-safety vulnerability prevalence, and every follow-up through 2026.
Microsoft 70%, Google/Android Rust, CISA Secure-by-Design (Jan 2026), NSA CSI, ONCD, DoD SWFT, EU CRA, Chrome CVE data, curl, UAF landscape.