New issue
Advanced search Search tips

Issue 907303 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 22
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in gpu::CommandBufferSetup::InitDecoder

Project Member Reported by ClusterFuzz, Nov 21

Issue description

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

Fuzzer: libFuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  gpu::CommandBufferSetup::InitDecoder
  gpu::CommandBufferSetup::RunCommandBuffer
  fuzzer_main.cc
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=609762:609763

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Nov 21

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, Nov 21

Labels: Test-Predator-Auto-Owner
Owner: geoffl...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/86d0abb79aaa0558dedac18fb78d5a3426641110 (Pass the correct have_context to GLES2Decoder::Destroy in the GPU fuzzer).

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 ClusterFuzz, Nov 21

Cc: piman@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 4 by bugdroid1@chromium.org, Nov 21

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

commit 95cc1e2bfef47090697c0e5fe50f935b413269a6
Author: Geoff Lang <geofflang@chromium.org>
Date: Wed Nov 21 19:47:06 2018

Re-create the Context in InitDecoder if it is null.

The context may have been destroyed because it was lost, recreate it for
the next iteration of the fuzzer.

BUG= 907303 
BUG= 907350 

Change-Id: Ie2acb7d8da68be7f96427766c697624e0d54bd7a
Reviewed-on: https://chromium-review.googlesource.com/c/1346730
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610179}
[modify] https://crrev.com/95cc1e2bfef47090697c0e5fe50f935b413269a6/gpu/command_buffer/tests/fuzzer_main.cc

Project Member

Comment 5 by ClusterFuzz, Nov 22

ClusterFuzz has detected this issue as fixed in range 610117:610181.

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

Fuzzer: libFuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  gpu::CommandBufferSetup::InitDecoder
  gpu::CommandBufferSetup::RunCommandBuffer
  fuzzer_main.cc
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=609762:609763
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=610117:610181

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 6 by ClusterFuzz, Nov 22

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

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

Sign in to add a comment