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

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

Similar to 737546 but with FXMEM_DefaultCalloc instead of FXMEM_DefaultAlloc.

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

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

Fuzzer: libFuzzer_pdf_codec_tiff_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e9000069f6
Crash State:
  TIFFReadBufferSetup
  TIFFFillTile
  TIFFReadEncodedTile
  
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=6115819900895232


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

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