Predator and CL did not provide any possible suspects.
Using Code Search for the file, "natives-external.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/v8/v8.git/+/8cfe45b6f1880008d09d4310458b6e6fcb0522dd

@adamk -- 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 474949:474979.

Detailed report: https://clusterfuzz.com/testcase?key=5152122932035584

Fuzzer: libfuzzer_v8_wasm_function_sigs_section_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  holder_ in natives-external.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=474907:474949
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=474949:474979

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5152122932035584


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

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