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 1871383 - glibc: Improve malloc implementation (includes Safe Linking)
Summary: glibc: Improve malloc implementation (includes Safe Linking)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.4
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: DJ Delorie
QA Contact: Martin Coufal
Jacob Taylor Valdez
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-23 01:26 UTC by Carlos O'Donell
Modified: 2023-05-16 10:59 UTC (History)
10 users (show)

Fixed In Version: glibc-2.28-215.el8
Doc Type: Enhancement
Doc Text:
.Security improvements added for `glibc` The `SafeLinking` feature has been added to `glibc`. As a result, it improves protection for the `malloc` family of functions against certain single-linked list corruption including the allocator's thread-local cache.
Clone Of:
Environment:
Last Closed: 2023-05-16 09:03:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2023:2955 0 None None None 2023-05-16 09:03:26 UTC
Sourceware 25733 0 P2 RESOLVED mallopt(M_MXFAST) can set global_max_fast to 0 2021-02-01 14:55:24 UTC

Description Carlos O'Donell 2020-08-23 01:26:28 UTC 
Backport the following commits to improve the malloc implementation:

a1a486d70ebcc47a686ff5846875eacad0940e41
Add Safe-Linking to fastbins and tcache

768358b6a80742f6be68ecd9f952f4b60614df96
Typo fixes and CR cleanup in Safe-Linking

49c3c37651e2d2ec4ff8ce21252bbbc08a9d6639
Fix alignment bug in Safe-Linking

6310d570bf20348135d09e1f9de84a9ae7d06f83
Add tests for Safe-Linking

b9cde4e3aa1ff338da7064daf1386b2f4a7351ba
malloc: ensure set_max_fast never stores zero [BZ #25733]
Comment 3 DJ Delorie 2021-03-02 15:41:57 UTC 
This upstream proposed patch should be included also:
https://sourceware.org/pipermail/libc-alpha/2020-August/116916.html
Comment 6 RHEL Program Management 2022-02-23 07:27:20 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 7 Carlos O'Donell 2022-02-23 14:05:37 UTC 
Reopening for planning purposes.
Comment 23 errata-xmlrpc 2023-05-16 09:03:05 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:2955
Note You need to log in before you can comment on or make changes to this bug.