Bug 2116960

Summary: glibc: Import bug fixes from glibc 2.34 upstream (snapshot 1) [rhel-9.2.0]
Product: Red Hat Enterprise Linux 9 Reporter: Arjun Shankar <ashankar>
Component: glibcAssignee: Arjun Shankar <ashankar>
Status: CLOSED ERRATA QA Contact: Sergey Kolosov <skolosov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: ashankar, codonell, dj, fweimer, markobri, mnewsome, pfrankli, sipoyare, skolosov
Target Milestone: rcKeywords: Bugfix, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.34-48.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:16:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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