public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/30843] potential use-after-free in getcanonname (CVE-2023-4806)
Date: Tue, 26 Sep 2023 22:52:23 +0000	[thread overview]
Message-ID: <bug-30843-131-WbR8MHfo14@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30843-131@http.sourceware.org/bugzilla/>

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

--- Comment #14 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.38/master branch has been updated by Siddhesh Poyarekar
<siddhesh@sourceware.org>:

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

commit f6445dc94da185b3d1ee283f0ca0a34c4e1986cc
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date:   Tue Sep 26 07:38:07 2023 -0400

    Document CVE-2023-4806 and CVE-2023-5156 in NEWS

    These are tracked in BZ #30884 and BZ #30843.

    Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
    (cherry picked from commit fd134feba35fa839018965733b34d28a09a075dd)

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

  parent reply	other threads:[~2023-09-26 22:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 15:32 [Bug network/30843] New: " siddhesh at sourceware dot org
2023-09-12 15:32 ` [Bug network/30843] " siddhesh at sourceware dot org
2023-09-13  3:18 ` sam at gentoo dot org
2023-09-14  6:45 ` xry111 at xry111 dot site
2023-09-14  9:56 ` siddhesh at sourceware dot org
2023-09-14 10:02 ` xry111 at xry111 dot site
2023-09-15 18:38 ` cvs-commit at gcc dot gnu.org
2023-09-15 19:19 ` cvs-commit at gcc dot gnu.org
2023-09-15 20:53 ` cvs-commit at gcc dot gnu.org
2023-09-15 22:25 ` cvs-commit at gcc dot gnu.org
2023-09-15 23:48 ` cvs-commit at gcc dot gnu.org
2023-09-16  0:50 ` cvs-commit at gcc dot gnu.org
2023-09-16  0:50 ` siddhesh at sourceware dot org
2023-09-25  0:40 ` romain.geissler at amadeus dot com
2023-09-25  5:55 ` fweimer at redhat dot com
2023-09-26 11:40 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:52 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-26 22:53 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:54 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:54 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:54 ` cvs-commit at gcc dot gnu.org
2023-12-11 16:29 ` m.novosyolov at rosalinux dot ru
2023-12-11 16:37 ` siddhesh at sourceware dot org

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-30843-131-WbR8MHfo14@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).