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

Issue 789926 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in content::WidgetInputHandlerManager::GetWidgetInputHandlerHost

Project Member Reported by ClusterFuzz, Nov 30 2017

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  content::WidgetInputHandlerManager::GetWidgetInputHandlerHost
  content::RenderWidget::OnDidOverscroll
  content::RenderWidgetInputHandler::DidOverscrollFromBlink
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=519986:520012

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 30 2017

Labels: OS-Windows
Project Member

Comment 2 by ClusterFuzz, Nov 30 2017

Components: Blink>Input Internals>Core
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, Nov 30 2017

Cc: shanmug...@samsung.com tzik@chromium.org
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Unify test classes to use PageTestBase by shanmuga.m@samsung.com - https://chromium.googlesource.com/chromium/src/+/b380fae11c46a727ab0e4b76f68bd7a83bd3b1da

Make blink::WebTaskRunner a subclass of base::SingleThreadTaskRunner by tzik@chromium.org - https://chromium.googlesource.com/chromium/src/+/c79a74b3793d40d532eea8f8574673a09f6f05f4

If this is incorrect, please apply the Test-Predator-Wrong-CLs label.
Owner: dtapu...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 30 2017

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

commit 2760614ef85f57db3ee1ffdefe50d4321b41f75b
Author: Dave Tapuska <dtapuska@chromium.org>
Date: Thu Nov 30 21:11:19 2017

Fix clusterfuzz crash on MojoInputMessages

The callsites were updated in
https://chromium-review.googlesource.com/c/chromium/src/+/793971 however
I left the DCHECK still in and didn't allow nullptr as the return value.
This caused the clusterfuzz failures.

BUG= 789926 , 789906 

Change-Id: I950f4ea72225faa0f9be3afbe022e0152079aa92
Reviewed-on: https://chromium-review.googlesource.com/801637
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#520685}
[modify] https://crrev.com/2760614ef85f57db3ee1ffdefe50d4321b41f75b/content/renderer/input/widget_input_handler_manager.cc

Project Member

Comment 6 by ClusterFuzz, Dec 1 2017

ClusterFuzz has detected this issue as fixed in range 520667:520710.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  content::WidgetInputHandlerManager::GetWidgetInputHandlerHost
  content::RenderWidget::OnDidOverscroll
  content::RenderWidgetInputHandler::DidOverscrollFromBlink
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=519986:520012
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=520667:520710

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

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 7 by ClusterFuzz, Dec 1 2017

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