New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 647649 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

old_size == 0 || wasm_memory_size_reference() <= old_size in assembler.cc

Project Member Reported by ClusterFuzz, Sep 16 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5380135836712960

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  old_size == 0 || wasm_memory_size_reference() <= old_size in assembler.cc
  
Regressed: V8: r39360:39361

Minimized Testcase (0.88 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96od_JK07XLn5ekWmWvpKb9Ezs1aNm1JvpKOd9cL9qw-uvh-ChxwhX_wFPwIF-QEjcWJctFJ5Sz4MD3Ho5JYwCb9rmK0nwP6TsUZKPKRms2BoWnQ67K_pV_pNBouQsui9nkub2hs1eajFRYoItwuALqtUFKEw?testcase_id=5380135836712960

Issue manually filed by: titzer

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Status: Started (was: Assigned)
Fix available in https://codereview.chromium.org/2347333002/. 
Waiting for 0xC to land 1st
Cc: bradnelson@chromium.org mtrofin@chromium.org
 Issue 650583  has been merged into this issue.
Project Member

Comment 4 by ClusterFuzz, Sep 28 2016

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

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

Comment 5 by bugdroid1@chromium.org, Sep 29 2016

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

commit df490c348433186f98bca50670b0b9094bd06ca1
Author: mtrofin <mtrofin@chromium.org>
Date: Thu Sep 29 00:48:11 2016

[wasm] Fix for cloning module heap size value

The module size is encoded as a HeapNumber, and needs to be
explicitly cloned.

BUG= chromium:647649 

Review-Url: https://codereview.chromium.org/2347333002
Cr-Commit-Position: refs/heads/master@{#39845}

[modify] https://crrev.com/df490c348433186f98bca50670b0b9094bd06ca1/src/wasm/wasm-module.cc
[add] https://crrev.com/df490c348433186f98bca50670b0b9094bd06ca1/test/mjsunit/regress/wasm/regression-647649.js

Project Member

Comment 6 by ClusterFuzz, Sep 29 2016

ClusterFuzz has detected this issue as fixed in range 39844:39845.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5380135836712960

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  old_size == 0 || wasm_memory_size_reference() <= old_size in assembler.cc
  
Regressed: V8: r39360:39361
Fixed: V8: r39844:39845

Minimized Testcase (0.88 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96od_JK07XLn5ekWmWvpKb9Ezs1aNm1JvpKOd9cL9qw-uvh-ChxwhX_wFPwIF-QEjcWJctFJ5Sz4MD3Ho5JYwCb9rmK0nwP6TsUZKPKRms2BoWnQ67K_pV_pNBouQsui9nkub2hs1eajFRYoItwuALqtUFKEw?testcase_id=5380135836712960

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 7 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment