New issue
Advanced search Search tips

Issue 829989 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 828524
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security
Proj-Servicification



Sign in to add a comment

Use of an invalid mutex in mojo::edk::MessagePipeDispatcher::Close

Project Member Reported by ClusterFuzz, Apr 6 2018

Issue description

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Use of an invalid mutex
Crash Address: 
Crash State:
  mojo::edk::MessagePipeDispatcher::Close
  base::internal::Invoker<base::internal::BindState<void
  base::internal::IncomingTaskQueue::RunTask
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=547645:547646

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 6 2018

Components: 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 2 by ClusterFuzz, Apr 6 2018

Labels: Test-Predator-Auto-Owner
Owner: yosin@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/fd236997d5000e6d74512fcb9a60f6157f0740b8 (Utilize selection_test() for "editing/deleting/transpose-empty.html").

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.
Labels: M-67 Pri-1
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 7 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

Comment 5 by yosin@chromium.org, Apr 9 2018

Cc: yosin@chromium.org
Labels: Test-Predator-Wrong-CLs
Owner: ----
Status: Untriaged (was: Assigned)
My patch mentioned in #c2 changes HTML for layout_test, it can not cause
this issue.
Components: -Internals>Core Internals>Services>Network
Owner: jam@chromium.org
Status: Assigned (was: Untriaged)
Another safe_browsing_network_context, probably a duplicates. 
Assign to jam@ for assessment.

Comment 7 by jam@chromium.org, Apr 9 2018

Mergedinto: 828524
Status: Duplicate (was: Assigned)
Yeah this looks the same, and is before the fix landed.
Project Member

Comment 8 by sheriffbot@chromium.org, Apr 10 2018

Labels: -reward-topanel reward-ineligible
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 17

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