Unable to find actual suspect through code search and also from the provided CL under regression range, hence adding appropriate label and leaving it as untriaged for further updates.

Thanks!

ClusterFuzz has detected this issue as fixed in range 555579:555606.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  net_quic_stream_factory_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=541160:541169
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=555579:555606

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

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.

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

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