Redo the task but still this issue is not fixed. could someone please take a look?
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 486753:487317.

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

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

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  SkIRect::width
  SkBlurMask::BoxBlur
  compute_bounds
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=370022:370027
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=486753:487317

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


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

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