New issue
Advanced search Search tips

Issue 765939 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Crash in sw::Thread::Thread

Project Member Reported by ClusterFuzz, Sep 16 2017

Issue description

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

Fuzzer: inferno_twister_c
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0xc8e00210
Crash State:
  sw::Thread::Thread
  sw::Renderer::initializeThreads
  sw::Renderer::updateConfiguration
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=496287:501540

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

Issue filed automatically.

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

Comment 1 by sheriffbot@chromium.org, Sep 17 2017

Labels: M-62
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 17 2017

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 3 by sheriffbot@chromium.org, Sep 17 2017

Labels: Pri-1

Comment 4 by palmer@chromium.org, Sep 20 2017

Cc: nicolasc...@google.com jbauman@google.com
Components: Internals>GPU>SwiftShader
Owner: jbau...@chromium.org
Status: Available (was: Untriaged)
Project Member

Comment 5 by sheriffbot@chromium.org, Sep 21 2017

Status: Assigned (was: Available)

Comment 6 by est...@chromium.org, Sep 28 2017

Cc: piman@chromium.org
Owner: sugoi@chromium.org
sugoi, piman, do you think you could help triage this stable blocker please? It looks like the author of a possible culprit CL is no longer working on Chrome so we need some help to get this fixed. Thanks!

Comment 7 by sugoi@chromium.org, Sep 29 2017

I'll take a look at it today or Monday.
Project Member

Comment 8 by bugdroid1@chromium.org, Oct 4 2017

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

commit 5955bc576d147925fb8966ca7b91a23f7c91591e
Author: Alexis Hetu <sugoi@google.com>
Date: Wed Oct 04 01:03:13 2017

Roll SwiftShader bc6ce4f..9d56da2

https://swiftshader.googlesource.com/SwiftShader.git/+log/bc6ce4f..9d56da2

BUG= chromium:763382 , chromium:763384 , chromium:763435 , chromium:765094 , chromium:765791 , chromium:765939 

TBR=kbr@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel,linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: Idd52bdc26eba54615838baf5dc65705a8a4be631
Reviewed-on: https://chromium-review.googlesource.com/699156
Commit-Queue: Alexis Hétu <sugoi@chromium.org>
Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506259}
[modify] https://crrev.com/5955bc576d147925fb8966ca7b91a23f7c91591e/DEPS

Project Member

Comment 9 by ClusterFuzz, Oct 4 2017

ClusterFuzz has detected this issue as fixed in range 506256:506290.

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

Fuzzer: inferno_twister_c
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0xc8e00810
Crash State:
  sw::Thread::Thread
  sw::Renderer::initializeThreads
  sw::Renderer::updateConfiguration
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=496287:501540
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=506256:506290

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

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 10 by ClusterFuzz, Oct 4 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5673981645684736 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 11 by sheriffbot@chromium.org, Oct 4 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -ReleaseBlock-Stable -M-62 M-63
Project Member

Comment 13 by sheriffbot@chromium.org, Jan 10 2018

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

Comment 14 by sheriffbot@chromium.org, Mar 27 2018

Labels: -Security_Impact-Beta -M-63 M-65 Security_Impact-Stable

Sign in to add a comment