Through code search on file painted_scrollbar_layer.cc, suspected CL is
https://chromium.googlesource.com/chromium/src/+/b504ebcca5ba3e17640034a59f17af670a530d7d

I could reproduce the crash on the suspected CL's parent:
https://chromium.googlesource.com/chromium/src/+/428cf9473ad24fc6e026ebe8fe12f0181c9c35d4

@enne, @khushalsagar, there some recent changes in related parts (Line 136, L 233) of the painted_scrollbar_layer.cc file. Could you please take a look?

ClusterFuzz has detected this issue as fixed in range 479886:479938.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Null-dereference WRITE
Crash Address: 0x00000000
Crash State:
  base::win::ForceCrashOnSigAbort
  FX_OutOfMemoryTerminate
  cc::PaintedScrollbarLayer::RasterizeScrollbarPart
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=440951:440953
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=479886:479938

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


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

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