New issue
Advanced search Search tips

Issue 844208 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 780156
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in gpu::raster::RasterDecoderImpl::DoTexStorage2D

Project Member Reported by ClusterFuzz, May 17 2018

Issue description

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

Fuzzer: libFuzzer_gpu_raster_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  gpu::raster::RasterDecoderImpl::DoTexStorage2D
  gpu::raster::RasterDecoderImpl::HandleTexStorage2D
  gpu::error::Error gpu::raster::RasterDecoderImpl::DoCommandsImpl<false>
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=559054:559074

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 17 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, May 17 2018

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 3 by ClusterFuzz, May 17 2018

Labels: Test-Predator-Auto-Owner
Owner: backer@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/a210e801d2389b72e762a446be8651700a71b330 (Cluster fuzz RasterDecoder).

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.

Comment 4 by piman@chromium.org, May 17 2018

This is same as https://bugs.chromium.org/p/chromium/issues/detail?id=780156, i.e. it doesn't affect production.

Comment 5 by backer@chromium.org, May 23 2018

Mergedinto: 780156
Status: Duplicate (was: Assigned)
Project Member

Comment 6 by ClusterFuzz, Jun 5 2018

ClusterFuzz has detected this issue as fixed in range 564128:564153.

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

Fuzzer: libFuzzer_gpu_raster_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  gpu::raster::RasterDecoderImpl::DoTexStorage2D
  gpu::raster::RasterDecoderImpl::HandleTexStorage2D
  gpu::error::Error gpu::raster::RasterDecoderImpl::DoCommandsImpl<false>
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=559054:559074
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=564128:564153

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

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.

Sign in to add a comment