Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Find it and CL did not provide any possible suspect.
Using code search for file "expat_xml_parse_fuzzer.cc" from frame #21 suspecting the below change
Review URL: https://codereview.chromium.org/2000993003

mmoroz@ - Observed some recent changes on this file so assigning to you, could you please check if this is caused with respect to your change, if not please help us in reassign the issue to the right owner.

Thanks!

Passing it over to expat owners (https://cs.chromium.org/chromium/src/third_party/expat/OWNERS).

ClusterFuzz has detected this issue as fixed in range 459024:459032.

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

Fuzzer: libfuzzer_expat_xml_parse_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  utf8_isName3
  normal_scanLt
  doContent
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=397275:397295
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=459024:459032

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94Evcw9XcKsWP-GlSbix_ajS1EF0BromqN9Ky6BXgTwuDZhC6qDB9kO69sYVDoHgtMmFjV_ooqmvRV8ypcjynzGp0WMdgxMygLFLpZhHK2Llm123JC6cpFUCLjqt-RWb4CU8q-tGG--x68CkJ82BNrK_Z3F2Xm0XFBgSu-URd0RJ7B03DI1d_Lj9Gjv-nG-T1Ia4l42yMp-efvgvqSfJs22byQRX_D1A6qTWrCf4YXOrpWXCi55CRxlLCFq2Q5eWiIsy9u3V800NtVos5NQpDGejY0L8vVy6pG4ESvnNMYATMTfXz_DA_vQw-sCD24crlsizYR0ItY3IV2Dr2LMvZzS79mTO3B6omIlMChiSos4xA_GtHU?testcase_id=6468082152505344


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

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

qingchengl fixed this in r459025