Bug 1710478 - glibc: Fix crash during wide stream buffer flush
Summary: glibc: Fix crash during wide stream buffer flush
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.1
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: 8.1
Assignee: Florian Weimer
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 1710460
Blocks: 1684559
TreeView+ depends on / blocked
 
Reported: 2019-05-15 15:13 UTC by Florian Weimer
Modified: 2023-07-18 14:30 UTC (History)
7 users (show)

Fixed In Version: glibc-2.28-61.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 1710460
Environment:
Last Closed: 2019-11-05 21:29: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 RHSA-2019:3513 0 None None None 2019-11-05 21:29:23 UTC
Sourceware 20568 0 None None None 2019-07-18 06:38:46 UTC

Description Florian Weimer 2019-05-15 15:13:54 UTC 
+++ This bug was initially created as a clone of Bug #1710460 +++

We need to incorporate this upstream fix:

commit 32ff397533715988c19cbf3675dcbd727ec13e18
Author: Andreas Schwab <schwab>
Date:   Tue May 14 17:14:59 2019 +0200

    Fix crash in _IO_wfile_sync (bug 20568)
    
    When computing the length of the converted part of the stdio buffer, use
    the number of consumed wide characters, not the (negative) distance to the
    end of the wide buffer.
Comment 5 Sergey Kolosov 2019-07-18 15:05:26 UTC 
Verified, the bug is reproducible in glibc-2.28-60.el8 and it has been fixed in glibc-2.28-61.el8
Comment 7 errata-xmlrpc 2019-11-05 21:29: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, 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/RHSA-2019:3513
Note You need to log in before you can comment on or make changes to this bug.