Predator did not provide any possible suspects.
Assigning to the concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/2a51ca1da61d7725ce337d32717b89508d121378..a5c138ca688efd003d0cf8525c1673d9b9c18c2d?pretty=fuller

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

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

ClusterFuzz has detected this issue as fixed in range 481516:481566.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !interface_object.IsEmpty() in V8PerContextData.cpp
  blink::V8PerContextData::CreateWrapperFromCacheSlowCase
  blink::V8PerContextData::CreateWrapperFromCache
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=479650:479666
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=481516:481566

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 4700404947615744 is verified as fixed, so closing issue.

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