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 2116960 - glibc: Import bug fixes from glibc 2.34 upstream (snapshot 1) [rhel-9.2.0]
Summary: glibc: Import bug fixes from glibc 2.34 upstream (snapshot 1) [rhel-9.2.0]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: glibc
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Arjun Shankar
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-09 15:40 UTC by Arjun Shankar
Modified: 2023-05-09 10:19 UTC (History)
9 users (show)

Fixed In Version: glibc-2.34-48.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 08:16:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2129005 0 unspecified CLOSED glibc: Do not fail name resolution if CNAMEs involve aliases which are not host names [rhel-9.2.0] 2023-06-27 06:24:49 UTC
Red Hat Issue Tracker RHELPLAN-130669 0 None None None 2022-08-09 15:47:10 UTC
Red Hat Product Errata RHBA-2023:2481 0 None None None 2023-05-09 08:16:39 UTC
Sourceware 28846 0 P2 RESOLVED CMSG_NXTHDR may trigger -Wstrict-overflow warning 2022-09-22 09:35:05 UTC

Internal Links: 2129005

Description Arjun Shankar 2022-08-09 15:40:52 UTC 
Import priority bug fixes from the glibc upstream 2.34 release branch.

The glibc upstream 2.34 branch is under active bug fix work and those fixes improve the quality of RHEL9.
Comment 1 Arjun Shankar 2022-08-09 15:42:03 UTC 
Ensure that the following commit is backported to upstream release branch and pulled into RHEL-9.2:

commit 9c443ac4559a47ed99859bd80d14dc4b6dd220a1
Author: Arjun Shankar <arjun>
Date:   Tue Aug 2 11:10:25 2022 +0200

    socket: Check lengths before advancing pointer in CMSG_NXTHDR
    
    The inline and library functions that the CMSG_NXTHDR macro may expand
    to increment the pointer to the header before checking the stride of
    the increment against available space.  Since C only allows incrementing
    pointers to one past the end of an array, the increment must be done
    after a length check.  This commit fixes that and includes a regression
    test for CMSG_FIRSTHDR and CMSG_NXTHDR.
    
    The Linux, Hurd, and generic headers are all changed.
    
    Tested on Linux on armv7hl, i686, x86_64, aarch64, ppc64le, and s390x.
    
    [BZ #28846]
    
    Reviewed-by: Siddhesh Poyarekar <siddhesh>
Comment 2 Florian Weimer 2022-09-22 09:30:19 UTC 
I expect that there will be a conflict in the import, which can be resolved by picking the original commit from the master branch instead. I filed bug 2129005 to track this.
Comment 7 errata-xmlrpc 2023-05-09 08:16:01 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (glibc bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2481
Note You need to log in before you can comment on or make changes to this bug.