public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/15142] Missing locking in _IO_cleanup
Date: Mon, 03 Jul 2023 09:08:46 +0000	[thread overview]
Message-ID: <bug-15142-131-SF9kye6zPk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15142-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15142

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
              Flags|security?                   |security-
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.38

--- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---
Fixed for 2.38 via:

commit af130d27099651e0d27b2cf2cfb44dafd6fe8a26
Author: Andreas Schwab <schwab@suse.de>
Date:   Tue Jan 30 10:16:00 2018 +0100

    Always do locking when accessing streams (bug 15142, bug 14697)

    Now that abort no longer calls fflush there is no reason to avoid locking
    the stdio streams anywhere.  This fixes a conformance issue and potential
    heap corruption during exit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-07-03  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 13:12 [Bug stdio/15142] New: " schwab@linux-m68k.org
2013-02-14 20:13 ` [Bug stdio/15142] " bugdal at aerifal dot cx
2014-03-25  9:24 ` schwab@linux-m68k.org
2014-06-13 18:49 ` fweimer at redhat dot com
2023-06-04 22:16 ` ppluzhnikov at google dot com
2023-07-03  9:08 ` fweimer at redhat dot com [this message]
2024-03-13 10:13 ` dvyukov at google dot com
2024-03-13 10:23 ` fweimer at redhat dot com
2024-03-13 10:28 ` dvyukov at google dot com
2024-03-13 10:43 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15142-131-SF9kye6zPk@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).