Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1594410 - (CVE-2018-12641) CVE-2018-12641 binutils: Stack Exhaustion in the demangling functions provided by libiberty
CVE-2018-12641 binutils: Stack Exhaustion in the demangling functions provide...
Status: NEW
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=20180413,reported=2...
: Security
Depends On: 1594413 1594415 1598557 1598561 1594412 1594414 1598560
Blocks: 1594411
  Show dependency treegraph
 
Reported: 2018-06-22 17:25 EDT by Laura Pardo
Modified: 2018-09-27 07:14 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Laura Pardo 2018-06-22 17:25:22 EDT
An issue was discovered in arm_pt in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_arm_hp_template, demangle_class_name, demangle_fund_type, do_type, do_arg, demangle_args, and demangle_nested_args. This can occur during execution of nm-new.


References:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763099 	
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85452 	
https://sourceware.org/bugzilla/show_bug.cgi?id=23058
Comment 1 Laura Pardo 2018-06-22 17:32:00 EDT
Created binutils tracking bugs for this issue:

Affects: fedora-all [bug 1594413]


Created mingw-binutils tracking bugs for this issue:

Affects: epel-all [bug 1594412]
Affects: fedora-all [bug 1594414]

Note You need to log in before you can comment on or make changes to this bug.