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 1449161 - crash in ssl3_GatherData
Summary: crash in ssl3_GatherData
Keywords:
Status: CLOSED DUPLICATE of bug 1446631
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nss
Version: 6.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: nss-nspr-maint
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-09 10:40 UTC by German Parente
Modified: 2022-03-13 14:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-26 11:41:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1435017 0 high CLOSED Segfault in libssl3.so during connection. 2021-02-22 00:41:40 UTC

Internal Links: 1435017

Description German Parente 2017-05-09 10:40:14 UTC
Description of problem:

we can see this crash at customer site:

Program terminated with signal 11, Segmentation fault.
#0  memcpy () at ../sysdeps/x86_64/memcpy.S:79
79		movw	%cx, (%rdi)
(gdb) bt
#0  memcpy () at ../sysdeps/x86_64/memcpy.S:79
#1  0x000000382981e1c7 in ssl3_GatherData (ss=0x167e8f0, flags=0) at ssl3gthr.c:210
#2  ssl3_GatherCompleteHandshake (ss=0x167e8f0, flags=0) at ssl3gthr.c:441
#3  0x000000382981ebe1 in ssl_GatherRecord1stHandshake (ss=0x167e8f0) at sslcon.c:98
#4  0x0000003829823e55 in ssl_Do1stHandshake (ss=0x167e8f0) at sslsecur.c:59
#5  0x0000003829824c2e in ssl_SecureRecv (ss=0x167e8f0, buf=0x1320220 "x\343\070%8", len=512, flags=0) at sslsecur.c:863
#6  0x0000003829829002 in ssl_Recv (fd=<value optimized out>, buf=0x1320220, len=512, flags=0, timeout=0) at sslsock.c:2711
#7  0x0000000000413454 in connection_read_ldap_data (conn=0x7f3ab418d310, op=0x148e330, tag=0x7f3a92ff6d58, remaining_data=0x7f3a92ff6d6c) at ldap/servers/slapd/connection.c:1834
#8  connection_read_operation (conn=0x7f3ab418d310, op=0x148e330, tag=0x7f3a92ff6d58, remaining_data=0x7f3a92ff6d6c) at ldap/servers/slapd/connection.c:1890
#9  0x0000000000413ff0 in connection_threadmain () at ldap/servers/slapd/connection.c:2264
#10 0x0000003827829c53 in _pt_root (arg=0x1649a70) at ../../../nspr/pr/src/pthreads/ptthread.c:216
#11 0x0000003825407aa1 in start_thread (arg=0x7f3a92ff7700) at pthread_create.c:301
#12 0x00000038250e8bcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115


Version-Release number of selected component (if applicable): nss-3.28.4-1.el6_9.x86_64

I can provide core file if needed. 

Regards,

German.


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