New issue
Advanced search Search tips

Issue 844828 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug-Security



Sign in to add a comment

Heap-use-after-free in gpu::gles2::GLES2Implementation::OnGpuControlLostContext

Project Member Reported by ClusterFuzz, May 19 2018

Issue description

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

Fuzzer: ochang_media2
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x6150000671a8
Crash State:
  gpu::gles2::GLES2Implementation::OnGpuControlLostContext
  gpu::CommandBufferProxyImpl::OnChannelError
  base::debug::TaskAnnotator::RunTask
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=559515:559525

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 19 2018

Labels: OS-Linux
Project Member

Comment 2 by ClusterFuzz, May 19 2018

Components: Blink>Scheduling Internals>Core
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 3 by sheriffbot@chromium.org, May 19 2018

Labels: M-68
Project Member

Comment 4 by sheriffbot@chromium.org, May 19 2018

Labels: ReleaseBlock-Stable
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
Project Member

Comment 5 by sheriffbot@chromium.org, May 19 2018

Labels: Pri-1

Comment 6 by mmoroz@chromium.org, May 21 2018

Owner: danakj@chromium.org
Status: Assigned (was: Untriaged)
danakj@, could you please and a look and / or help to find an owner?
Project Member

Comment 7 by sheriffbot@chromium.org, May 30 2018

Labels: -Security_Impact-Head Security_Impact-Beta
Project Member

Comment 8 by ClusterFuzz, Jun 2 2018

ClusterFuzz has detected this issue as fixed in range 563664:563689.

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

Fuzzer: ochang_media2
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x6150000671a8
Crash State:
  gpu::gles2::GLES2Implementation::OnGpuControlLostContext
  gpu::CommandBufferProxyImpl::OnChannelError
  base::debug::TaskAnnotator::RunTask
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=559515:559525
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=563664:563689

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

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.
Project Member

Comment 9 by ClusterFuzz, Jun 2 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4677658684948480 is verified as fixed, so closing issue as verified.

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

Comment 10 by sheriffbot@chromium.org, Jun 2 2018

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Project Member

Comment 11 by sheriffbot@chromium.org, Jun 8 2018

Labels: Merge-Request-68
Project Member

Comment 12 by sheriffbot@chromium.org, Jun 8 2018

Labels: -Merge-Request-68 Hotlist-Merge-Review Merge-Review-68
This bug requires manual review: M68 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), kariahda@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Merge-Review-68 Merge-Rejected-68
Seems like nothing to merge. 
Labels: -ReleaseBlock-Stable -M-68 M-69
Project Member

Comment 15 by sheriffbot@chromium.org, Sep 8

Labels: -Restrict-View-SecurityNotify allpublic
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

Sign in to add a comment