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

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

 Issue 675436  has been merged into this issue.

Please take a look at this. Thank you.

chrishtr: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

I can't reproduce on Linux ASAN so far. Will try Mac ASAN per reported
bug tomorrow.

I can reproduce on Linux now. Fix coming soon.

ClusterFuzz testcase 5578952040251392 is verified as fixed, so closing issue.

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

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

commit ad9aa972891607894db3a60370afd8b19445df0c
Author: chrishtr <chrishtr@chromium.org>
Date: Tue Jan 10 01:43:49 2017

When setting needsRepaint, don't stop at non-stacking composited PaintLayers.

Content may paint into an ancestor graphics layer.

BUG= 675205 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

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

[add] https://crrev.com/ad9aa972891607894db3a60370afd8b19445df0c/third_party/WebKit/LayoutTests/paint/invalidation/remove-subframe-composited-nonstacking-ancestor-expected.txt
[add] https://crrev.com/ad9aa972891607894db3a60370afd8b19445df0c/third_party/WebKit/LayoutTests/paint/invalidation/remove-subframe-composited-nonstacking-ancestor.html
[modify] https://crrev.com/ad9aa972891607894db3a60370afd8b19445df0c/third_party/WebKit/Source/core/layout/compositing/GraphicsLayerUpdater.cpp
[modify] https://crrev.com/ad9aa972891607894db3a60370afd8b19445df0c/third_party/WebKit/Source/core/paint/PaintLayer.cpp
[modify] https://crrev.com/ad9aa972891607894db3a60370afd8b19445df0c/third_party/WebKit/Source/core/paint/PaintLayerTest.cpp

ClusterFuzz has detected this issue as fixed in range 441984:442831.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x613000087508
Crash State:
  blink::visualRectForDisplayItem
  blink::PaintController::commitNewDisplayItems
  blink::GraphicsLayer::paint
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_chrome&range=436306:436323
Fixed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_chrome&range=441984:442831

Minimized Testcase (1.76 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94YsQvZQOnK5TpJ5EUNKMYfAtLzpNLl7EMjyQoq_dQPWEEJyhqdnzdSYAtCRvbJJyw59IDMwgQuTltKElbwHK5YbDIUE6xw01inkBMheF8dUbOqaCCvq1KuXU_546A9z0BwRjpaAbo_VBAOzMKR1tpGutq-tw?testcase_id=6575560445919232

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.

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

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.