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

Issue 882110 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Security



Sign in to add a comment

Crash in glvmRasterOpRead

Project Member Reported by ClusterFuzz, Sep 8

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: UNKNOWN READ
Crash Address: 0x0002475307a0
Crash State:
  glvmRasterOpRead
  glvmInterpretFPTransformFour
  gldLLVMFPTransform
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=568152:568171

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Sep 8

Components: 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 sheriffbot@chromium.org, Sep 8

Labels: M-69 Target-69
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 8

Labels: Pri-1
Cc: ccameron@chromium.org
Owner: senorblanco@chromium.org
Status: Assigned (was: Untriaged)
senorblanco: Is it possible for https://chromium.googlesource.com/chromium/src/+/df18b96b443774d232e39ead6cbd81c848b8563c to have triggered this? I can't tell if it's an issue in Apple's OpenGL or the calling code.
A bit more of the stack:
   #0 0x7fff89370e6c in glvmRasterOpRead
     #1 0x7fff8936b145 in glvmInterpretFPTransformFour
     #2 0x7fff8a15f3d7 in gldLLVMFPTransform
    #3 0x7fff8a173ad4 in gldLLVMVecPolyRender
    #4 0x7fff8a1594ec in gldRenderFillPolygonPtr
    #5 0x1369fed2f  (<unknown module>)
    #5 0x7fff87912331 in gleFlushAtomicFunc
    #6 0x7fff879a37b5 in glDrawArrays_GL3Exec

This is in Apples software renderer IIUC (gldLLVM is "gl driver llvm"). So this is an Apple bug.
Out of interest, when does the Apple software renderer get used? I thought Macs were always either accelerated or blacklisted (no GL).
I should emphasize the IIUC part of #5, but we use Apple's SW renderer in VMWare at times.
Project Member

Comment 8 by sheriffbot@chromium.org, Oct 2

senorblanco: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: kbr@chromium.org zmo@chromium.org
Components: -Internals>Skia Internals>GPU>VendorSpecific
Owner: ----
Status: Available (was: Assigned)
Given that it's a bug in the Apple software renderer, I don't think there's much I can do. I have had no reports of instability on real GPUs from this change.

If no GPU is available (e.g., VMWare) we should really be using the Skia software renderer and software compositor for 2D content, not GL with the Apple software renderer. It would likely be much faster, as well.
Labels: -Pri-1 Pri-2
Status: WontFix (was: Available)
Project Member

Comment 11 by ClusterFuzz, Oct 9

Labels: Needs-Feedback
ClusterFuzz testcase 5735040506658816 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.
Project Member

Comment 12 by sheriffbot@chromium.org, Jan 9

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