Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1383297 - (CVE-2016-6323) CVE-2016-6323 glibc: Missing unwind info in __startcontext causes infinite loop in _Unwind_Backtrace
CVE-2016-6323 glibc: Missing unwind info in __startcontext causes infinite lo...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160804,reported=2...
: Security
Depends On: 1383298 1383311
Blocks: 1383299
  Show dependency treegraph
 
Reported: 2016-10-10 07:36 EDT by Adam Mariš
Modified: 2016-10-21 10:06 EDT (History)
13 users (show)

See Also:
Fixed In Version: glibc 2.25
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-10-10 07:57:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2016-10-10 07:36:07 EDT
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 07:36:40 EDT
Created glibc tracking bugs for this issue:

Affects: fedora-all [bug 1383298]
Comment 2 Adam Mariš 2016-10-10 07:57:17 EDT
Affects only ARM EABI (32-bit) platforms.
Comment 3 Adam Mariš 2016-10-10 07:59:47 EDT
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.