clemensh could you help triage please? Thanks!

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Liftoff is not enabled yet, so this is not a release blocker and not security relevant.

ClusterFuzz has detected this issue as fixed in range 517321:517335.

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

Fuzzer: libFuzzer_v8_wasm_code_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  dst == src in liftoff-assembler.cc
  v8::internal::wasm::StackTransferRecipe::TransferStackSlot
  v8::internal::wasm::LiftoffAssembler::MergeStackWith
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514360:514382
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=517321:517335

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

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

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

Fix: https://chromium-review.googlesource.com/766353

ClusterFuzz testcase 6022136602034176 is verified as fixed, so closing issue as verified.

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