Adjacent buffers in structs and classes are not protected from overflow, in part to prevent breaking backwards compatibility.
Google also produced LeakSanitizer (LSan, memory leaks), ThreadSanitizer (TSan, data races and deadlocks), MemorySanitizer (MSan, uninitialized memory), and UndefinedBehaviorSanitizer (UBSan, undefined behaviors, with fine-grained control).
[15][16][17] Similar to KASan, there are kernel-specific versions of LSan, MSan, TSan, as well as completely original kernel sanitizers such as KFENCE and KCSan.
One common way to use a sanitizer is to combine it with fuzzing, which generates inputs likely to trigger bugs.
[21] Chromium and Firefox developers are active users of AddressSanitizer;[21][22] the tool has found hundreds of bugs in these web browsers.