Bug 1722216 - glibc: During exit, skip wide buffer handling for legacy stdio handles
Summary: glibc: During exit, skip wide buffer handling for legacy stdio handles
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 29
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Weimer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1722215
TreeView+ depends on / blocked
 
Reported: 2019-06-19 17:31 UTC by Florian Weimer
Modified: 2019-09-21 05:46 UTC (History)
10 users (show)

Fixed In Version: glibc-2.29.9000-29.fc31 glibc-2.29-17.fc30 glibc-2.28-35.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1722215
Environment:
Last Closed: 2019-09-21 05:46:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1688841 0 unspecified CLOSED glibc's free() crashes with ulimit -s unlimited when exiting from java -version 2021-02-22 00:41:40 UTC
Sourceware 24228 0 None None None 2019-08-07 16:12:02 UTC

Internal Links: 1688841

Description Florian Weimer 2019-06-19 17:31:20 UTC
+++ This bug was initially created as a clone of Bug #1722215 +++

This commit, which went into glibc 2.23, introduces wide stream buffer deallocation during the exit produces:

commit a601b74d31ca086de38441d316a3dee24c866305
Author: Paul Pluzhnikov <ppluzhnikov>
Date:   Sat Aug 8 16:27:58 2015 -0700

    In preparation for fixing BZ#16734, fix failure in misc/tst-error1-mem
    when _G_HAVE_MMAP is turned off.

This results in an out-of-bounds access with unpredictable consequences during process shutdown for i386 binaries which enable the legacy stdio handles.

Usually, this is supposed to happen only for very old binaries, but it turns out that the launchers in OpenJDK 8 are linked in such a way that this happens for them as well.  See bug 1688841 for details.

To maximize compatibility, we should backport the eventual upstream fix to glibc.

Comment 1 Fedora Update System 2019-09-05 09:20:16 UTC
FEDORA-2019-2e9a65b50a has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2e9a65b50a

Comment 2 Fedora Update System 2019-09-05 12:53:25 UTC
glibc-2.29-22.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2e9a65b50a

Comment 3 Fedora Update System 2019-09-06 09:44:23 UTC
FEDORA-2019-8532718f88 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-8532718f88

Comment 4 Fedora Update System 2019-09-06 12:33:58 UTC
glibc-2.29-22.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2019-09-06 13:21:50 UTC
glibc-2.28-39.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8532718f88

Comment 6 Fedora Update System 2019-09-21 01:42:21 UTC
glibc-2.28-39.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


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