Find it did not find provide any possible suspect.
Assigning to the concern owner from the regressed range -
https://chromium.googlesource.com/chromium/src/+log/801601cb2944e82342f0a1939ad3e76f9eba4902..d932f9ab78a0e790b4228b70a48e4fc6cac31e49?pretty=fuller

Suspecting the Commit# 
https://chromium.googlesource.com/chromium/src/+/6d9a122c6a4ad8f6bf4c1c688b2ea06c09c50a2a

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

This only impacts Stable and Beta. Head is not impacted.
I guess this is due to some memory leaks fixed in head.

This is not worth to fix. Right?

ClusterFuzz has detected this issue as fixed in range 443824:443836.

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

Fuzzer: libfuzzer_pdf_codec_icc_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  pdf_codec_icc_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=420535:420584
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=443824:443836

Minimized Testcase (0.19 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95BjVWbFYFcMYgmJdX7m1U7c3LQHvMIYSXOdK1XPPhJY_XeJcxQiQ5CV83rGuZeE7wv-o7d3Y7L9wTv1ph3ii_M0JiVpE3y-Wx8sJGCnzZp069HJuWNSAIHAUp35uIGdJvA_hlCh-wtwayDkDCqb_orLAPlCg?testcase_id=5551124317995008

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 5551124317995008 is verified as fixed, so closing issue.

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