New issue
Advanced search Search tips

Issue 917991 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in spvtools::opt::InstructionFolder::UnaryOperate

Project Member Reported by ClusterFuzz, Dec 27

Issue description

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

Fuzzer: libFuzzer_spvtools_opt_size_fuzzer
Fuzz target binary: spvtools_opt_size_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  spvtools::opt::InstructionFolder::UnaryOperate
  spvtools::opt::InstructionFolder::FoldScalars
  spvtools::opt::InstructionFolder::FoldInstructionToConstant
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=580304:580310

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 27

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, Dec 27

Cc: dsinclair@chromium.org vmi...@chromium.org 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, Dec 27

Cc: 31666...@users.noreply.github.com d...@everburning.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Update OpPhi instructions after splitting block. (#1783) by 31666470+s-perron@users.noreply.github.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/ce644d4a2484fe66e53f5b744ebc4d0d5d49e1ca

Remove using std::<foo> statements. (#1756) by dj2@everburning.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/a5a5ea0e2dfce9c755a88af1074ebe68a44d2ed9

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
Cc: -31666...@users.noreply.github.com -d...@everburning.com
Owner: stevenperron@google.com
Status: Assigned (was: Untriaged)

Comment 5 by stevenperron@google.com, Jan 16 (6 days ago)

Status: Started (was: Assigned)
https://github.com/KhronosGroup/SPIRV-Tools/pull/2293

Comment 6 by stevenperron@google.com, Jan 17 (5 days ago)

Status: Fixed (was: Started)
Project Member

Comment 7 by ClusterFuzz, Jan 18 (4 days ago)

ClusterFuzz has detected this issue as fixed in range 623961:623974.

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

Fuzzer: libFuzzer_spvtools_opt_size_fuzzer
Fuzz target binary: spvtools_opt_size_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  spvtools::opt::InstructionFolder::UnaryOperate
  spvtools::opt::InstructionFolder::FoldScalars
  spvtools::opt::InstructionFolder::FoldInstructionToConstant
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=580304:580310
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=623961:623974

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

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 8 by ClusterFuzz, Jan 18 (4 days ago)

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