This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

This looks like it's quite deep in skia. hcm: can you pleas help triage? Thanks!

over to Yuqian for a look at the AAA code, though we haven't been changing that for a while...

I see. According to the stacktrace, I called SkRasterPipelineBlitter::blitAntiH and then something bad happened. I think SkRasterPipelineBlitter is quite new, and it might be a good idea to keep mtklein@ in the loop.

I don't think we have any reason to suspect the scan converter.  Let's dup this on the other byte_tables bug for now.

ClusterFuzz has detected this issue as fixed in range 487641:487678.

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

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x61908002fd98
Crash State:
  _sk_byte_tables_avx
  RunBasedAdditiveBlitter::flush
  SkScan::AAAFillPath
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=482916:483010
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=487641:487678

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


See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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