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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/378375d2e5b50aa6d36f8cacd5b24ff0e9d263c3 ([scanner] Templatize scan functions by encoding).

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.

ClusterFuzz has detected this issue as fixed in range 55225:55226.

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

Fuzzer: decoder_langfuzz
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x5562140309d0
Crash State:
  Bad-cast to CharacterStream<uint16_t>' (aka 'CharacterStream<unsigned short>') from v8::internal::RelocatingCharacterStream<unsigned char>
  v8::internal::wasm::AsmJsParser::AsmJsParser
  v8::internal::AsmJsCompilationJob::ExecuteJobImpl
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=55216:55217
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=55225:55226

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

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

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

(fixing automation problems)

This one was found by internal fuzzers too (mbarbella_js_mutation, ochang_js_fuzzer, inferno_js_fuzzer)

@awhalley there is nothing in this bug that says this was found by internal fuzzers or when it was found. Can you please provide pointers for that?

Beyond the fact that it was found by other fuzzers, the cast was an accidental left-over unnecessary (unused) downcast, so there was no security risk. Additionally the CL was reverted for performance reasons a day or 2 later.

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