Looks like 8c14bf7d37bec879a5caa162f2c72a303da1a6e0 might be related.

ClusterFuzz has detected this issue as fixed in range 435261:438085.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6493990628360192

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  SkIRect::offset
  ApplyImageFilter
  cc::GLRenderer::UpdateRPDQWithSkiaFilters
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=422899:423265
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=435261:438085

Minimized Testcase (0.38 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97YL4-etZUauqqEmMUvIwdS-b-a3iIuiqbpMM5hMkkxNWwB6tKXk3cyNJAzDlfCJXzVnDjJ8H_baKEoQO_tMvodcXwgaSqfx9Jo73DF3f6mi1_Ms1BE0HPrIjMbvP1BTj85L-CdYzZqrHV0HjRj850aKWqsCA?testcase_id=6493990628360192

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

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