New issue
Advanced search Search tips

Issue 887216 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 30
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in position_mark

Project Member Reported by ClusterFuzz, Sep 20

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  position_mark
  position_around_base
  position_cluster
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=587601:587602

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Sep 20

Components: Blink>Fonts
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, Sep 20

Labels: Test-Predator-Auto-Owner
Owner: h...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/d54494cbad8d5ff0a8cd74024902c8bd86258ae4 (Roll clang 338452:340925).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Owner: e...@chromium.org
Maybe the Clang roll uncovered an existing problem with the code.

-> eae for third_party/harfbuzz-ng
Status: WontFix (was: Assigned)
Non-security int overflows are considered WontFix.
Project Member

Comment 5 by ClusterFuzz, Dec 7

Labels: Needs-Feedback
ClusterFuzz testcase 6416224316293120 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.

Sign in to add a comment