While out-of-bounds accesses shouldn't happen in practice, a recent
bitset change uncovered that bounds checks were missing.
Note that CookieInclusionStatus is passed as an int32 via mojo, and
only the NUM_WARNING_REASONS and NUM_EXCLUSION_REASONS are read.
See https://github.com/llvm/llvm-project/pull/120685/files for info on
the bitset hardening change.
Change-Id: Iaea68330479a7f6c3340d4300893dd00fbbed181
Bug: 385924889
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6142073
Reviewed-by: Steven Bingler <bingler@chromium.org>
Commit-Queue: Matt Reichhoff <mreichhoff@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1401936}
6fbfb0308c