Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1383297 (CVE-2016-6323) - CVE-2016-6323 glibc: Missing unwind info in __startcontext causes infinite loop in _Unwind_Backtrace
Summary: CVE-2016-6323 glibc: Missing unwind info in __startcontext causes infinite lo...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2016-6323
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1383298 1383311
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 11:36 UTC by Adam Mariš
Modified: 2019-09-29 13:57 UTC (History)
13 users (show)

Fixed In Version: glibc 2.25
Clone Of:
Environment:
Last Closed: 2016-10-10 11:57:17 UTC
Embargoed:

Attachments (Terms of Use)

Description Adam Mariš 2016-10-10 11:36:07 UTC 
Missing unwind info in __startcontext was found that can lead to infinite loop in _Unwind_Backtrace. Generating stack trace in application code compiled with gccgo can trigger this, causing the affected process hanging up instead of error message.

Upstream bug:

https://sourceware.org/bugzilla/show_bug.cgi?id=20435
Comment 1 Adam Mariš 2016-10-10 11:36:40 UTC 
Created glibc tracking bugs for this issue:

Affects: fedora-all [bug 1383298]
Comment 2 Adam Mariš 2016-10-10 11:57:17 UTC 
Affects only ARM EABI (32-bit) platforms.
Comment 3 Adam Mariš 2016-10-10 11:59:47 UTC 
Created glibc-arm-linux-gnu tracking bugs for this issue:

Affects: fedora-all [bug 1383311]
Note You need to log in before you can comment on or make changes to this bug.