New issue
Advanced search Search tips

Issue 868584 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jul 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in blink::EventTarget::IsTopLevelNode

Project Member Reported by ClusterFuzz, Jul 27

Issue description

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::EventTarget::IsTopLevelNode
  blink::WheelEvent::preventDefault
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=578690:578695

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jul 27

Labels: OS-Windows
Project Member

Comment 2 by ClusterFuzz, Jul 27

Components: Blink>DOM
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 3 by ClusterFuzz, Jul 27

Labels: Test-Predator-Auto-Owner
Owner: sahel@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/667f001d9507c6ba636c93b1a831f333f5f475d8 (Add use counter for document level wheel event listeners.).

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 4 by ClusterFuzz, Jul 28

Labels: Fuzz-Blocker ReleaseBlock-Beta M-70
This crash occurs very frequently on windows platform and is likely preventing the fuzzer ifratric-browserfuzzer-v3 from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.
Project Member

Comment 5 by ClusterFuzz, Jul 28

Labels: OS-Mac
Project Member

Comment 6 by bugdroid1@chromium.org, Jul 30

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

commit fac41025a9b9a43d31c66d6f4eccf92649ec51ba
Author: Sahel Sharify <sahel@chromium.org>
Date: Mon Jul 30 22:00:10 2018

Check currentTarget != null befire checking if it is top level or not.

Bug:  868584 
Change-Id: Ifa831ebeb3c7b2b86dc9cb5d56d122085eabfec1
Reviewed-on: https://chromium-review.googlesource.com/1155148
Commit-Queue: Sahel Sharify <sahel@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579185}
[modify] https://crrev.com/fac41025a9b9a43d31c66d6f4eccf92649ec51ba/third_party/blink/renderer/core/events/wheel_event.cc

Project Member

Comment 7 by ClusterFuzz, Jul 31

ClusterFuzz has detected this issue as fixed in range 579184:579185.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::EventTarget::IsTopLevelNode
  blink::WheelEvent::preventDefault
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=578690:578695
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=579184:579185

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

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 8 by ClusterFuzz, Jul 31

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