New issue
Advanced search Search tips

Issue 703832 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Security



Sign in to add a comment

Bad-free in gpu::MemoryBufferBacking::~MemoryBufferBacking

Project Member Reported by ClusterFuzz, Mar 21 2017

Issue description

Comment 1 by rsesek@chromium.org, Mar 21 2017

Components: Internals>GPU>Internals
Owner: geoffl...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 2 by sheriffbot@chromium.org, Mar 22 2017

Labels: M-59
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 22 2017

Labels: ReleaseBlock-Beta
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 22 2017

Labels: Pri-1
Cc: cwallez@chromium.org jmad...@chromium.org
Labels: -Pri-1 -ReleaseBlock-Beta Pri-2
This code is not released yet, removing the release block labels.

Comment 6 by rsesek@chromium.org, Mar 22 2017

geofflang: Do you mean that this code is guarded by a build/runtime flag, or just that the code hasn't yet made it to a release channel? If it's the latter, then the right labels are M-59 ReleaseBlock-Beta, because we don't want to release M59 Beta without this fixed.
This code is guarded by a runtime flag and is still experimental.  Release would be M60 or later.
Project Member

Comment 8 by ClusterFuzz, Mar 23 2017

ClusterFuzz has detected this issue as fixed in range 458862:458900.

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

Fuzzer: libfuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Bad-free
Crash Address: 0x602000003290
Crash State:
  gpu::MemoryBufferBacking::~MemoryBufferBacking
  gpu::MemoryBufferBacking::~MemoryBufferBacking
  gpu::Buffer::~Buffer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=458075:458147
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=458862:458900

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94ASzdtV2mGSMeiq3xrjmKOeXXE-ByEKm_6Hlv4rnrktKHzIxX3BQxX93aAliwqr1Slpzb-Ayx0nTHPr-XYB6r2ULHE0nPcHW5W7cPma3c7QiX6_a4fNUqj_2YnusIX1XB600ANWiEvS-mEJUBJ4vWI7wte-yzbdVE2lg_2_k_D4T1WpsleL_NWDN6G1RPQDu-0Z-nRP3GFbnU-rG8s86yV9Ot8QO4NX9mrLqX07hEwOSbf9egqBxX2LDyczTVtsz_H2eGpN8xSo6ipTo7xjAKkZ4rgO6oJoQHOGeV64B5Vpdn7wTpUuFE13UuNbyAF_eEdiJxfM-7_nRgBDZEzHa3A8TsS146jRB1sVznE4RiD6Oqv9pFEF3Cf3X9FFl632r8nCYy1iR5z5i-BmL9iJwbSkheE_Q?testcase_id=4862080495910912


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 9 by ClusterFuzz, Mar 23 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4862080495910912 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 10 by sheriffbot@chromium.org, Mar 23 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Project Member

Comment 11 by sheriffbot@chromium.org, Jun 29 2017

Labels: -Restrict-View-SecurityNotify 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