This is a critical security issue. 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

+awhalley@ for M61 merge review

A friendly reminder that M61 Beta promotion is coming soon! Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix and request a merge to M61 branch 3163 latest by 4:00 PM PT, Thursday (07/27). Thank you.

(Security Sheriff Triage)
Quite possibly a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=748464

Fixed in https://chromium.googlesource.com/chromium/src/+/ba05045c920078d04b7135144dd14c649bc73727

ClusterFuzz has detected this issue as fixed in range 489314:489347.

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

Fuzzer: attekett_surku_fuzzer
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Heap-use-after-free READ 1
Crash Address: 0x078d75d0
Crash State:
  ui::AXPlatformNodeWin::Destroy
  ui::AXSystemCaretWin::`scalar deleting destructor'
  content::LegacyRenderWidgetHostHWND::~LegacyRenderWidgetHostHWND
  
Sanitizer: address (ASAN)

Recommended Security Severity: Critical

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=489161:489186
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=489314:489347

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


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.

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

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

I'm very sorry to say that this was caught by our internal fuzzers within 48 hours of this report.

Oh, do you have a test case?

test case in report crashes.  looking into it now.

I can crash Stable with the supplied test case, but can _not_ crash Canary (62.0.3179.0 (Official Build) canary (64-bit) (cohort: Clang-64)) or master.

awhalley, can you verify what version of chrome crashes?

Sorry for the confusion - moving back to Verified per OOB discussion.

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