Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/79a60792014bc051ad11f0fc5507741a2a842e7e ([wasm] Implement I64Atomic Binary operations on ARM64).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

After triage, please leave a comment on if the bug can have security implications.

Bug disabled in prod, editing labels accordingly. 

Access misalignment for atomic operations should trap, moving to medium severity as this should not cause an out of bounds access.

ClusterFuzz has detected this issue as fixed in range 55137:55138.

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

Fuzzer: binaryen_wasm_fuzzer
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  address % access_size == 0 in simulator-arm64.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm64_dbg&range=52483:52484
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm64_dbg&range=55137:55138

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

See https://github.com/google/clusterfuzz-tools 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 5356570440105984 is verified as fixed, so closing issue as verified.

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

(dupe of some of the other bugs we've been getting from this fuzzer, but with a different signature)

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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