Find it and CL did not provide any possible suspects.
Using Code Search for the file, "sfntly_fuzzer" assigning to the concern owner.

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

@thestig -- 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 450164:450196.

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

Fuzzer: libfuzzer_sfntly_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  sfntly_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=414164:414272
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=450164:450196

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95mQBwyN_OWbtoTXyp6OeTy8zmbs5hBEfBLFut7gHGhROSMRhuXtIPWP2IMdytyQGW44vDlhOsrH9SWgIkI8DibMVa4QfqE-jgdJNIQyRjsuE6P3a_ItYrPsrZinP2ZaUyZt6WS1c7ptHXlI08Sj1Bg8Zg6IIvMfnF3vej7HmbxbNlmkEwUl_sAV7IKeAwQElch_EPAyJXR1HM6545btoKpn-3esvxZQ1-y4qKWh2p0IiX3kMkvzr7_Zmi73fQ4qQq2qghN0axp7IevdmKmsh_4AmtIAs1PTukoPj78NYT0iJzKJn9D-QZthMXl6q-BNBvhHKzKYV98K4Y4QD4VvIxJ6P1igKeUX-eLNBy4r4HBBP1hzpw?testcase_id=6399515839168512


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

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