RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1441689 - gawk killed by SIGABRT
Summary: gawk killed by SIGABRT
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gawk
Version: 7.3
Hardware: All
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Martin Klusoň
Petr Bokoc
URL:
Whiteboard:
Depends On:
Blocks: 1461115
TreeView+ depends on / blocked
 
Reported: 2017-04-12 13:24 UTC by Paulo Andrade
Modified: 2021-01-15 07:59 UTC (History)
8 users (show)

Fixed In Version: gawk-4.0.2-5.el7
Doc Type: Bug Fix
Doc Text:
Gawk no longer terminates unexpectedly Prior to this update, a bug in the *gawk* utility could sometimes cause it to perform an out of bounds write, which resulted in *gawk* being killed by a `SIGABRT` signal. This bug has been fixed, and *gawk* is no longer being terminated unexpectedly.
Clone Of:
: 1461115 (view as bug list)
Environment:
Last Closed: 2021-01-15 07:33:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Paulo Andrade 2017-04-12 13:24:32 UTC
*** Error in `gawk': free(): invalid next size (fast): 0x0000000002dd99b0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7c503)[0x7faf4d117503]
gawk(valinfo+0x74)[0x40e434]
gawk(print_vars+0xbe)[0x40e65e]
gawk(dump_vars+0x31)[0x40e691]
gawk(main+0x11a4)[0x408984]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7faf4d0bcb35]
gawk[0x408aa5]

  RHEL 7.3 is missing the second chunk of the commit at:
http://git.savannah.gnu.org/cgit/gawk.git/commit/?id=9fe77c4d6778eb6b0ad377abf702e3472cd40564
and on certain uncommon conditions might write out of
bounds, due to ensuring there is place to write one byte,
but writing two.

Comment 6 Kamil Dudka 2017-05-29 08:53:07 UTC
Looks like an easy to fix off-by-one error.


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