Predator and CL did not provide any possible suspects.
Using Code Search for the file, "tif_getimage.c" assigning to the concern owner.
Suspecting Commit#
https://pdfium.googlesource.com/pdfium.git/+/4fc34fa8376dd5cd119606ba6e0dd7e08d23ac38

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

This is caused by 7726a581626bbb72d6ab294ae1adbad4ca10dfb0.

Link not working, I mean:
https://pdfium-review.googlesource.com/c/6552/

 Issue 739770  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 486555:486672.

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

Fuzzer: libFuzzer_pdf_codec_tiff_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e9000070e7
Crash State:
  gtTileContig
  TIFFReadRGBAImageOriented
  CTiffContext::Decode
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=481576:482713
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=486555:486672

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


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

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