Issue metadata
Sign in to add a comment
|
Heap-use-after-free in SkImage::getTextureHandle |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5388510940102656 Fuzzer: marty_html_twiddler Job Type: mac_asan_chrome Platform Id: mac Crash Type: Heap-use-after-free READ 8 Crash Address: 0x6070001d3730 Crash State: SkImage::getTextureHandle cc::GpuImageDecodeCache::RunPendingContextThreadOperations cc::GpuImageDecodeCache::ReduceCacheUsage Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=500790:500792 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5388510940102656 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 11 2017
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
,
Sep 11 2017
,
Sep 12 2017
ClusterFuzz has detected this issue as fixed in range 500986:501046. Detailed report: https://clusterfuzz.com/testcase?key=5388510940102656 Fuzzer: marty_html_twiddler Job Type: mac_asan_chrome Platform Id: mac Crash Type: Heap-use-after-free READ 8 Crash Address: 0x6070001d3730 Crash State: SkImage::getTextureHandle cc::GpuImageDecodeCache::RunPendingContextThreadOperations cc::GpuImageDecodeCache::ReduceCacheUsage Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=500790:500792 Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=500986:501046 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5388510940102656 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.
,
Sep 12 2017
,
Sep 12 2017
ClusterFuzz testcase 5388510940102656 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 13 2017
,
Sep 15 2017
,
Sep 15 2017
This bug requires manual review: M62 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 15 2017
Approving merge for M62. Branch:3202
,
Sep 19 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. 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
,
Sep 20 2017
Making this Merge-TBD since it's unclear exactly what is being merged.
,
Sep 21 2017
The regression range points to commits on Sep 9, so this was likely a trunk regression that was fixed very quickly. No merge should be needed.
,
Sep 25 2017
Thanks - removing Merge-TBD label.
,
Oct 5 2017
,
Dec 20 2017
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
,
Mar 27 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Sep 11 2017