Predator and CL did not provide any possible suspects.
Using Code Search for the file, "SkRect.h" assigning to the concern owner.

Suspecting Commit#
https://skia.googlesource.com/skia.git/+/ca49067a3378b5c0364817c4198c063de05a331a

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

Lowering priority on non-security integer overflows- while unexpected rendering behavior is not ideal, it is also not work that can be prioritized at this time.

ClusterFuzz has detected this issue as fixed in range 485152:485153.

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

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

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  SkIRect::width
  just_trans_clamp
  SkBitmapProcInfo::init
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=440242:440280
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=485152:485153

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


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

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