New issue
Advanced search Search tips

Issue 883181 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Crash in v8::internal::interpreter::BytecodeRegisterOptimizer::GetRegisterInfo

Project Member Reported by ClusterFuzz, Sep 12

Issue description

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x55dc1cfb63e8
Crash State:
  v8::internal::interpreter::BytecodeRegisterOptimizer::GetRegisterInfo
  v8::internal::interpreter::BytecodeRegisterOptimizer::DoLdar
  v8::internal::interpreter::BytecodeArrayBuilder::LoadAccumulatorWithRegister
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=55808:55809

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Sep 12

Components: Blink>JavaScript>Interpreter
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, Sep 12

Labels: Test-Predator-Auto-Owner
Owner: ofrobots@google.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/2363cdfefeb643285cbe8593b7c17d80e5d06cd9 ([tracing] do not add traces when disabled).

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 ClusterFuzz, Sep 12

ClusterFuzz has detected this issue as fixed in range 55811:55812.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x55dc1cfb63e8
Crash State:
  v8::internal::interpreter::BytecodeRegisterOptimizer::GetRegisterInfo
  v8::internal::interpreter::BytecodeRegisterOptimizer::DoLdar
  v8::internal::interpreter::BytecodeArrayBuilder::LoadAccumulatorWithRegister
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=55808:55809
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=55811:55812

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

See https://github.com/google/clusterfuzz-tools 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 4 by ClusterFuzz, Sep 12

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

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

Comment 5 by sheriffbot@chromium.org, Sep 12

Labels: Pri-1
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 12

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
I don't see how my change could have caused this, and I certainly didn't fix it. It seems like there might be some flakiness in this test?
Project Member

Comment 8 by sheriffbot@chromium.org, Dec 19

Labels: -Restrict-View-SecurityNotify 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