Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

I went to reproduce with a useful local build and it appears that Chromium's v8 build is currently failing in ubsan builds. Since we already know what to check I'm going to just add a manual check here and use a normal debug build to make sure we get a fix, but the ubsan build having issues is quite annoying.

ClusterFuzz has detected this issue as fixed in range 562984:562985.

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

Fuzzer: tokenfuzz_pdf_curated
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Pointer-overflow
Crash Address: 
Crash State:
  af_loader_load_glyph
  af_autofitter_load_glyph
  FT_Load_Glyph
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=551565:551567
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=562984:562985

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

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

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