New issue
Advanced search Search tips

Issue 917630 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

Null-dereference WRITE in dawn_wire::server::Server::OnMapWriteAsyncCallback

Project Member Reported by ClusterFuzz, Dec 23

Issue description

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

Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: dawn_wire_server_and_frontend_fuzzer
Job Type: x86_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x00000014
Crash State:
  dawn_wire::server::Server::OnMapWriteAsyncCallback
  dawn_wire::server::ForwardBufferMapWriteAsync
  dawn_native::BufferBase::CallMapWriteCallback
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=617852:617861

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
 
Project Member

Comment 1 by ClusterFuzz, Dec 23

Cc: kainino@chromium.org cwallez@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 2 by ClusterFuzz, Dec 23

Labels: Test-Predator-Auto-Owner
Owner: jiawei.s...@intel.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/5e811aeee56483b64d66d2325fd37c14a55b600c (Add render pass color and depth stencil attachment descriptor).

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.
Cc: jiawei.s...@intel.com
Components: Internals>GPU>Dawn
Owner: cwallez@chromium.org
Project Member

Comment 4 by ClusterFuzz, Dec 27

ClusterFuzz has detected this issue as fixed in range 619011:619012.

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

Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: dawn_wire_server_and_frontend_fuzzer
Job Type: x86_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x00000014
Crash State:
  dawn_wire::server::Server::OnMapWriteAsyncCallback
  dawn_wire::server::ForwardBufferMapWriteAsync
  dawn_native::BufferBase::CallMapWriteCallback
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=617852:617861
Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=619011:619012

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 5 by ClusterFuzz, Dec 27

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5753432128094208 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