Predator and CL did not provide any possible suspect.
Using Code Search for the file, "cmstypes.c" assigning to the concern owner.
Suspecting Commit#
https://pdfium.git.corp.google.com/pdfium.git/+/e3f237740fd8bea50b4a6f37f56455dfa0328546#

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

Not related to my changes, but being fixed.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/11e15a648963d343125c2bb95369f4bfa178ea69

commit 11e15a648963d343125c2bb95369f4bfa178ea69
Author: pdfium-deps-roller <pdfium-deps-roller@chromium.org>
Date: Mon Feb 27 23:34:37 2017

Roll src/third_party/pdfium/ 9162ff85c..ce32acfa1 (4 commits).

https://pdfium.googlesource.com/pdfium.git/+log/9162ff85c323..ce32acfa1507

$ git log 9162ff85c..ce32acfa1 --date=short --no-merges --format='%ad %ae %s'
2017-02-27 npm Spacing nit in libtiff patch
2017-02-27 npm LCMS upstream patch to fix integer overflows
2017-02-27 npm Add public API for creating a Type1 font
2017-02-27 tsepez Explicitly tag fxjs native objects.

Created with:
  roll-dep src/third_party/pdfium
BUG= 696430 , 695830 

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

TBR=dsinclair@chromium.org

Review-Url: https://codereview.chromium.org/2718223002
Cr-Commit-Position: refs/heads/master@{#453390}

[modify] https://crrev.com/11e15a648963d343125c2bb95369f4bfa178ea69/DEPS

ClusterFuzz has detected this issue as fixed in range 453381:453413.

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

Fuzzer: libfuzzer_pdf_codec_icc_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  Type_MPEmatrix_Read
  ReadMPEElem
  ReadPositionTable
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=420535:420584
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=453381:453413

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95CVZ2xGYivJ2w5BX8GXFWDZ9iZ-lisyiHlBa0CIQMk81gck79o5sVUljV_SNUmyw5XNHPDeC4u2w4s5csMTTQW3cMh13_K7yfZlNxcmeqFrBr7bYhsPyM8v-JSp2p4yVJ2069ZCjcCwS4HxEFg23QzdN8LZ5YerjcZ1plJyHC90pfDTfv-RBT_aeVWst3iUiYvJxyBZQNEzWCpaBxGdYCAga1_pycvr6k0aHbiNirmsoCWCz34gXnvMOHuOBiBRHkdqAS4VID15UnXBgv7cw28t0PTZcHZaPsBOjMHiyrCySAbkRGPwOW_62uHRcvlSoW-ukTuQEg-KWEvokvtqE6e4el9VEfMMmK2_hqf6AFJX8BPqAo?testcase_id=5899279404367872


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

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