Predator and CL could not provide any possible suspects.
Using Code Search for the file, "synthetic_gesture_target_base.cc" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/233e1b3593cd4a9565e2ffef1a9ec97207d740e2

@sadrul -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

I think this only happens with --enable-gpu-benchmarking command-line option? Is there a way to confirm? (I couldn't find a way to show the cmdline flags used in the fuzz test)

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

ClusterFuzz has detected this issue as fixed in range 506298:506317.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  PointIsWithinContents(web_wheel.x, web_wheel.y). Mouse wheel position is not wit
  content::SyntheticGestureTargetBase::DispatchInputEventToPlatform
  content::SyntheticSmoothMoveGesture::ForwardMouseWheelInputEvents
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=398573:398771
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=506298:506317

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

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

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

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

commit dbb2669b32ab27554437f7129f7200464459cfb9
Author: Dave Tapuska <dtapuska@chromium.org>
Date: Tue Nov 14 22:19:14 2017

Pass some validity checks in the gpu_benchmarking extension for input.

Throw an exception if the ranges aren't in the correct bounds. This
check is the same that is done for the tap method.

BUG= 719157 

Change-Id: I3771ef49e679812dcaf4d87c9d1806e4703c9eb2
Reviewed-on: https://chromium-review.googlesource.com/700419
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516456}
[modify] https://crrev.com/dbb2669b32ab27554437f7129f7200464459cfb9/content/renderer/gpu/gpu_benchmarking_extension.cc
[add] https://crrev.com/dbb2669b32ab27554437f7129f7200464459cfb9/third_party/WebKit/LayoutTests/fast/events/synthetic-events/gpu-benchmarking-validity.html