Security context

Highlights

Memory Corruption: 25 prior fixes. Scrutinize any change in this area.

src/libANGLE/validationES.cpp: most-fixed (29 issues). Treat as high-risk during review.

129 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

Memory Corruption: Parallel link operations, unhandled out-of-memory errors, and resource recycling during context teardown frequently trigger use-after-free or memory corruption. Robust synchronization and state-flushing are required to safely manage resource lifecycles.

Integer Overflow: Calculations involving instance counts, draw attributes, offsets, and texture dimensions often suffer from 32-bit integer truncation and wrap-arounds. This allows attackers to bypass size validation checks and trigger downstream out-of-bounds writes.

Information Disclosure: Bypassing robust resource initialization allows read operations (such as texture copies, read pixels, or frame buffer clears) to expose uncleared GPU memory containing stale graphics data from other contexts or processes.