New issue
Advanced search Search tips

Issue 911956 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Dec 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference WRITE in StartAlignedOffsetForLine

Project Member Reported by ClusterFuzz, Dec 5

Issue description

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

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

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000050
Crash State:
  StartAlignedOffsetForLine
  blink::SetStaticPositions
  blink::LineBreaker::SkipLeadingWhitespace
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=613694:613698

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 5

Components: Blink>Layout
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, Dec 7

ClusterFuzz has detected this issue as fixed in range 614465:614471.

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

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

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000050
Crash State:
  StartAlignedOffsetForLine
  blink::SetStaticPositions
  blink::LineBreaker::SkipLeadingWhitespace
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=613694:613698
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=614465:614471

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

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, Dec 7

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 6678269908484096 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