New issue
Advanced search Search tips

Issue 818476 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 719162
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Security



Sign in to add a comment

Crash in gldRenderFillPolygonPtr

Project Member Reported by ClusterFuzz, Mar 4 2018

Issue description

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

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

Crash Type: UNKNOWN READ
Crash Address: 0x000230da3000
Crash State:
  gldRenderFillPolygonPtr
  glDrawArrays_IMM_GL3Exec
  gpu::gles2::GLES2DecoderImpl::DoDrawArrays
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=521561:521602

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 4 2018

Components: Internals>GPU>Internals
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 2 by ClusterFuzz, Mar 4 2018

Labels: Test-Predator-Auto-Owner
Owner: tsepez@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/a788b14fe2b1e3b94f31c7f20279dee1ebc37353 (Restrict command processed by syscall_broker process.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 4 2018

Labels: M-65
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 4 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, Mar 4 2018

Labels: Pri-1
Cc: awhalley@chromium.org
+awhalley@, is this M65 stable blocker? Pls note we're cutting M65 stable RC tomorrow, Monday @11:00 AM.
Labels: -Security_Impact-Beta -ReleaseBlock-Stable -M-65 M-66 Security_Impact-Stable
We can track this for 66

Comment 8 by kenrb@chromium.org, Mar 5 2018

Owner: piman@chromium.org
This looks a lot like  issue 719162 , which people eventually ended up giving up on because it appeared to be a Mac driver bug and nobody could independently reproduce it.

piman@: Do you care to look at another one of these?

If we decide to close it similarly then it should get a Clusterfuzz-Ignore label as well.

Comment 9 by piman@chromium.org, Mar 5 2018

Mergedinto: 719162
Status: Duplicate (was: Assigned)
This is effectively the same issue.
Labels: ClusterFuzz-Ignore
We need Clusterfuzz-Ignore or the bug will keep getting filed every time CF hits it.
Project Member

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

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