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

Issue 853542 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Null-dereference READ in mov_find_next_sample

Project Member Reported by ClusterFuzz, Jun 17 2018

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  mov_find_next_sample
  mov_read_packet
  ff_read_packet
  
Sanitizer: memory (MSAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: brajkumar@chromium.org
Components: Internals>Media>FFmpeg
Labels: -Type-Bug M-69 Test-Predator-Wrong Type-Bug-Regression
Owner: hubbe@chromium.org
Status: Assigned (was: Untriaged)
This issue looks similar to  bug 848713 , hence assigning to the same owner.

hubbe@ Could you please take a look in to this issue?

Thanks!
Project Member

Comment 2 by ClusterFuzz, Jun 22 2018

ClusterFuzz has detected this issue as fixed in range 569276:569278.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  mov_find_next_sample
  mov_read_packet
  ff_read_packet
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=560380:560384
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=569276:569278

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

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 3 by ClusterFuzz, Jun 22 2018

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

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

Sign in to add a comment