Integer-overflow in blink::LineWidth::WrapNextToShapeOutside |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4868156823961600 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_ubsan_chrome Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: blink::LineWidth::WrapNextToShapeOutside blink::LineWidth::FitBelowFloats blink::BreakingContext::CommitAndUpdateLineBreakIfNeeded Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=370022:370027 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4868156823961600 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Sep 22 2017
Not a security issue in code that is being replaced. WontFix.
,
Sep 29 2017
ClusterFuzz testcase 4868156823961600 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.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Nov 7 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by msrchandra@chromium.org
, Sep 19 2017Labels: Test-Predator-Wrong CF-NeedsTriage M-63