Predator could not provide any possible suspects.
Assigning to concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/0804d72cf549935431044fc07c83105753bf912e..af0dc05d501cafad6ce25a775ada2559cabd12f0?pretty=fuller&n=10000

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

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

This is a FreeType issue, and was already fixed with FreeType commit http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=0aca17cf53f099f9ea34b3797949076073b60b5d . We just need to roll to pick up the fix. There was a roll in progress, but I'm not sure what happened to that. Will check.

ClusterFuzz has detected this issue as fixed in range 500968:501035.

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

Fuzzer: libFuzzer_pdf_font_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  Ins_ALIGNRP
  TT_RunIns
  TT_Hint_Glyph
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=483358:483512
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=500968:501035

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

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

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