New issue
Advanced search Search tips

Issue 799329 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Null-dereference READ in cc::ServiceImageTransferCacheEntry* cc::TransferCacheDeserializeHelper::GetEntry

Project Member Reported by ClusterFuzz, Jan 5 2018

Issue description

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  cc::ServiceImageTransferCacheEntry* cc::TransferCacheDeserializeHelper::GetEntry
  cc::PaintOpReader::Read
  cc::DrawImageOp::Deserialize
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=527100:527110

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jan 5 2018

Labels: Test-Predator-Auto-Owner
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/8b8436915204fb6de906de699e125123bf9b4b94 (OOP: Image Support).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 2 by ClusterFuzz, Jan 5 2018

Components: Internals>Compositing
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 ClusterFuzz, Jan 8 2018

Labels: OS-Mac
Project Member

Comment 4 by bugdroid1@chromium.org, Jan 8 2018

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

commit c732605e7d88b7586e12e405cd56172edb1d3261
Author: Eric Karl <ericrk@chromium.org>
Date: Mon Jan 08 17:53:02 2018

OOP: Fix incorrect init in fuzzer

We weren't correctly setting up the deserialize_options due to a typo.

R=enne@chromium.org

Bug:  799329 
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: If1ad4d8833966c7aeadaf58bec9a5320c4c63c55
Reviewed-on: https://chromium-review.googlesource.com/853219
Commit-Queue: enne <enne@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#527669}
[modify] https://crrev.com/c732605e7d88b7586e12e405cd56172edb1d3261/cc/paint/paint_op_buffer_eq_fuzzer.cc

Project Member

Comment 5 by ClusterFuzz, Jan 9 2018

ClusterFuzz has detected this issue as fixed in range 527668:527671.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  cc::ServiceImageTransferCacheEntry* cc::TransferCacheDeserializeHelper::GetEntry
  cc::PaintOpReader::Read
  cc::DrawImageOp::Deserialize
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=527100:527110
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=527668:527671

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

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, Jan 9 2018

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