Predator and CL could not provide any possible suspects.

Using the code search for the file, “congestion_controller_feedback_fuzzer.cc” assigning to concern owner.

Suspecting Commit# https://webrtc.git.corp.google.com/src.git/+/92ea95e34af5966555903026f45164afbd7e2088

mbonadei@-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.


Thank You...

I am assigning this to Stefan since he has more context on that.

The following revision refers to this bug:
  https://webrtc.googlesource.com/src.git/+/d7e251378b4aea7e43261e1a756a29445b891f2e

commit d7e251378b4aea7e43261e1a756a29445b891f2e
Author: Stefan Holmer <stefan@webrtc.org>
Date: Thu Nov 23 14:18:38 2017

Fix potential overflow in congestion controller fuzzer.

Bug:  chromium:787753 
Change-Id: I43d765379216db35f3df748b16599b34bffd388f
Reviewed-on: https://webrtc-review.googlesource.com/25480
Reviewed-by: Björn Terelius <terelius@webrtc.org>
Commit-Queue: Stefan Holmer <stefan@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#20851}
[modify] https://crrev.com/d7e251378b4aea7e43261e1a756a29445b891f2e/test/fuzzers/congestion_controller_feedback_fuzzer.cc

ClusterFuzz has detected this issue as fixed in range 519012:519020.

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

Fuzzer: libFuzzer_congestion_controller_feedback_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  webrtc::FuzzOneInput
  webrtc_fuzzer_main.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=407738:407796
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=519012:519020

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

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

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

 Issue 653699  has been merged into this issue.