public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/release/2.34/master] NEWS: Mention bug fixes for 29039/30745/30843
Date: Sat, 23 Dec 2023 17:38:43 +0000 (GMT)	[thread overview]
Message-ID: <20231223173844.3F0B23858C60@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=43ac0f94f19a55bd2454f64b95275b3206ca6c1b

commit 43ac0f94f19a55bd2454f64b95275b3206ca6c1b
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sat Dec 23 06:27:50 2023 -0800

    NEWS: Mention bug fixes for 29039/30745/30843

Diff:
---
 NEWS | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/NEWS b/NEWS
index af73ed99f5..3c8bec80a1 100644
--- a/NEWS
+++ b/NEWS
@@ -124,6 +124,7 @@ The following bugs are resolved with this release:
   [28953] nss: Protect against errno changes in function lookup
   [29029] nptl: poll() spuriously returns EINTR during thread
     cancellation and with cancellation disabled
+  [29039] Corrupt DTV after reuse of a TLS module ID following dlclose with unused TLS
   [29069] libc: fstatat64_time64_statx wrapper broken on MIPS N32 with
     -D_FILE_OFFSET_BITS=64 and -D_TIME_BITS=64
   [29078] <dlfcn.h> functions unusable during early auditing
@@ -160,6 +161,8 @@ The following bugs are resolved with this release:
   [30151] gshadow: Matching sgetsgent, sgetsgent_r ERANGE handling
   [30163] posix: Fix system blocks SIGCHLD erroneously
   [30305] x86_64: Fix asm constraints in feraiseexcept
+  [30745] Slight bug in cache info codes for x86
+  [30843] potential use-after-free in getcanonname (CVE-2023-4806)
   [31184] FAIL: elf/tst-tlsgap
   [31185] Incorrect thread point access in _dl_tlsdesc_undefweak and _dl_tlsdesc_dynamic

                 reply	other threads:[~2023-12-23 17:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231223173844.3F0B23858C60@sourceware.org \
    --to=hjl@sourceware.org \
    --cc=glibc-cvs@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).