New issue
Advanced search Search tips

Issue 875877 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Use-of-uninitialized-value in Sk4fXfermode<ColorDodge>::xfer32

Project Member Reported by ClusterFuzz, Aug 20

Issue description

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

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

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  Sk4fXfermode<ColorDodge>::xfer32
  SkARGB32_Shader_Blitter::blitRect
  SkScan::FillIRect
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=582653:582655

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Components: Internals>Skia
Labels: M-70
Owner: hcm@google.com
Status: Assigned (was: Untriaged)
hcm: Can you take a look at this crash? Thanks.
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 21

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

Labels: Pri-1
Cc: hcm@google.com
Components: Internals>Compositing
Owner: ----
I don't think this problem is created by Skia's code, but having trouble pinpointing where things go wrong in code further down the stack trace.  Also a better bisect would be really helpful.
Labels: Needs-Bisect
Cc: sugoi@google.com
sugoi@ -- I know this is a long shot, but any possibility that this may have been caused by your CL: https://chromium-review.googlesource.com/1128207
Cc: kjlubick@chromium.org
Owner: sugoi@chromium.org
sugoi - feel free to re-assign if this is not caused by the (longshot) CL above.
Cc: -sugoi@google.com infe...@chromium.org
This is another case of a leftover "--use-gl=osmesa" on Linux MSAN on Clusterfuzz. These have been changed to "-use-gl=swiftshader", so this issue may be obsolete (not sure if it will recover by itself).
Status: WontFix (was: Assigned)
Flag is removed, but it sticks with testcase, closing.
Project Member

Comment 12 by ClusterFuzz, Sep 7

Labels: Needs-Feedback
ClusterFuzz testcase 5182307754049536 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
Labels: ClusterFuzz-Ignore
Labels: -ClusterFuzz-Ignore
Oops, wrong bug
Project Member

Comment 15 by ClusterFuzz, Oct 12

ClusterFuzz has detected this issue as fixed in range 598841:598866.

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

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

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  Sk4fXfermode<ColorDodge>::xfer32
  SkARGB32_Shader_Blitter::blitRect
  SkScan::FillIRect
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=582653:582655
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=598841:598866

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

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 16 by sheriffbot@chromium.org, Dec 8

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