Predator did not provide any possible suspects.
Assigning to the concern owner from the below CL --
https://chromium.googlesource.com/chromium/src/+log/5f12b627c3a67b59f3a42a3374b3255ebe1abe19..ddefb10bee663f8d240c999309f37cc2f96d2e92?pretty=fuller

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

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

That is just a revert CL because of test breakage.
Reassigned to enne@, who's the original author.

If a revert revealed this, then this is likely a long standing bug.  That code stopped being run in the patch and started being reused in the revert.

Handing to mtklein.  I don't know if Skia WontFixes this sort of thing, but just FYI.

Skia at least decreases priority on these non-security int overflows... if someone has an idea and quick fix, awesome, but these come and go and often cannot be prioritized with other work.

ClusterFuzz has detected this issue as fixed in range 468540:468550.

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

Fuzzer: miaubiz_svg_fuzzer
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  SkIRect::width
  SkNoPixelsDevice::resetForNextPicture
  SkCanvas::resetForNextPicture
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=465194:465196
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=468540:468550

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


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

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