Find it and CL did not provide any possible suspects.
Using Code Search for the file, "wasm-call.cc" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/v8/v8/+/55fc5c0c327cec8385503bdcda0cfcee7f51213e

@titzer -- 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 443222:443277.

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

Fuzzer: libfuzzer_v8_wasm_call_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  Disposing the isolate that is entered by a thread in wasm-call.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=430572:430611
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=443222:443277

Minimized Testcase (0.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97DPELZl6ofshPaLwyxMSB0qbB_cEDse3q2fY4gL_pxKGAbnHkOPqYIcTC6SqxfiXD1HCD1FCfa9L8m6zaszQ6OjJkD7uZXZrhFVuo52ogVaXcxo50s3ttxAwXCL_27KuD7bHc4ewLEiSU0e5wie1_DsTP-H9X0lDiovWvlNvl5n6VVDYVg8cpDYNTUc_Hl_K6SHCx8eoGawt6mVy5j0BoidYtPbDeQgDFiayRlZNDMWuRa0Pr4ZMiFGU4v5296HGCLixV2dEdSSCp0iSVhttQQl6FoGcUevDFbNTPiOY8zyAblHOJI714MaevdZgJZdvwKCPSYbCGGqewScokcT3fM_-TPlpetdbHs9KXyaeboRUKByREpsPrsmdZiyxhd9WrhLYj0MV6i5eVXYGlkyfGGkxBvAw?testcase_id=6240873773006848

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 6240873773006848 is verified as fixed, so closing issue.

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