New issue
Advanced search Search tips

Issue 833056 link

Starred by 1 user
Status: Duplicate
Merged: issue 833122
Owner:
h...@chromium.org
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Requested allocation size 0x168817b9469c in v8::internal::JSArrayBuffer::SetupAllocatingData

Project Member Reported by ClusterFuzz, Apr 14 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5546661401853952

Fuzzer: mbarbella_webgl
Job Type: linux_asan_chrome_gpu
Platform Id: linux

Crash Type: Requested allocation size 0x168817b9469c
Crash Address: 
Crash State:
  v8::internal::JSArrayBuffer::SetupAllocatingData
  v8::internal::ConstructBuffer
  v8::internal::Builtin_Impl_ArrayBufferConstructor
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_gpu&range=550607:550608

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, Apr 14 2018

Components: Blink>JavaScript
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, Apr 14 2018

Labels: Test-Predator-Auto-Owner
Owner: h...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/1f109d9c516640dda836493b24fd033da64411ff (Roll clang 328716:329921.).

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.
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 14 2018

Labels: M-67
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 14 2018

Labels: ReleaseBlock-Stable
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Comment 5 by sheriffbot@chromium.org, Apr 14 2018

Labels: Pri-1
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 18 2018

Labels: -Security_Impact-Head Security_Impact-Beta

Comment 7 by h...@chromium.org, Apr 18 2018

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

Comment 8 by sheriffbot@chromium.org, Jul 30

Labels: -Restrict-View-SecurityTeam allpublic
This bug has been closed for more than 14 weeks. Removing security view restrictions.

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

Sign in to add a comment