Found by WASM code fuzzer. Andreas, could you triage further?

ClusterFuzz has detected this issue as fixed in range 421457:421501.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6616466164285440

Fuzzer: afl_v8_wasm_code_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000060
Crash State:
  v8::internal::wasm::WasmFullDecoder::CreateOrMergeIntoPhi
  v8::internal::wasm::WasmFullDecoder::BreakTo
  v8::internal::wasm::WasmFullDecoder::DecodeFunctionBody
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=415614:415641
Fixed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=421457:421501

Minimized Testcase (0.08 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96HfL_iCNk27byuzf1zvj4Dnp7MHJShuo4rg5PrE_MTfzYOA8FqY4tkeAcPUqIyE_k9C-THSxkOG7M21wfiSX9jefDL7-mO4gqm2SJoUsCMp-pgz0AxERPkgUsu0koOvSaZHIy34j35S7zKBIBtMQ4pEOXtwQ?testcase_id=6616466164285440

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

This was not really fixed; it's just that the binary format changed, causing the test case to be rejected earlier. After manually fixing the test, I ran into and fixed another bug (see https://codereview.chromium.org/2376153003/)

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot