This looks similar to some other non-security int overflow stacks we have come and go and are not critical to fix. Lowering priority.

ClusterFuzz has detected this issue as fixed in range 485877:485889.

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  SkPerspIter::next
  ClampX_ClampY_filter_persp
  BitmapProcShaderContext::shadeSpan
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=412915:412948
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=485877:485889

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 5226481029742592 is verified as fixed, so closing issue.

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