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

Issue 833122 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Requested allocation size 0xf0e5c9d492700 in base::UncheckedMalloc

Project Member Reported by ClusterFuzz, Apr 15 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_gpu
Platform Id: linux

Crash Type: Requested allocation size 0xf0e5c9d492700
Crash Address: 
Crash State:
  base::UncheckedMalloc
  sk_malloc_flags
  SkMallocPixelRef::MakeAllocate
  
Sanitizer: address (ASAN)

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

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 15 2018

Components: Internals>Core Internals>Skia
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 15 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 15 2018

Labels: M-67
Project Member

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

Cc: r...@chromium.org
I see a couple of these since the Clang roll. Duping them against this one.

I'm not sure who is a good person to debug this though.

Comment 8 by aarya@google.com, Apr 23 2018

Status: WontFix (was: Assigned)
Needed parse signatures in CF after
https://github.com/llvm-mirror/compiler-rt/commit/85f6bace7a20b03d7a754d83a1b655b504eee0e3

Comment 9 by aarya@google.com, Apr 23 2018

Cc: reed@google.com ifratric@google.com
 Issue 834750  has been merged into this issue.

Comment 10 by aarya@google.com, Apr 23 2018

Cc: bbudge@chromium.org eholk@chromium.org palmer@chromium.org
 Issue 833896  has been merged into this issue.
Project Member

Comment 11 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