Find it and CL did not provide any possible suspect.

Assigning to concern owner who worked on similar wasm_fuzzer.

@ahaas -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 447739:447795.

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

Fuzzer: libfuzzer_v8_wasm_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  v8_wasm_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=445689:445740
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=447739:447795

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94L2sMBrKgkgUrZJRApuZZEjsphggSRF9szy1LbYyqVkx0GqTFeIR8W4Q-YRUBLnQlbwCk9Y0cHqAHyjebQuCSid5VdLKGKEJd8uclfkFyItZydXGEbsQ_5255HXIiqmZ8w0aT6_RDnv-fMMd7lEYe52Y-HxQgQZM3EbUBaq88DI9XpALDnWVmZN9xTSjLV9x1ZS8760IbP95nt_cidTC-bxvZPHLvKmhsi28uvQqQxrHnxg8pSQtpiJhBEfxV03UyBMO8sT9IfUgEkJ2XpDk692UeX4qzCRQxHDmDROtAGfR9CzCRCt4j_wFlz09je7-9ZPeo6fBXf7q9kwZ-IloNHe9rCehreSNi0X4YyaUcx_-919DI?testcase_id=5713958796525568


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.