public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "camila.camargodematos at canonical dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/29605] Regression in NSCD backend of getaddrinfo
Date: Mon, 08 Jan 2024 11:11:25 +0000 [thread overview]
Message-ID: <bug-29605-131-VA6xE6WWtI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29605-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29605
Camila Camargo de Matos <camila.camargodematos at canonical dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |camila.camargodematos@canon
| |ical.com
--- Comment #13 from Camila Camargo de Matos <camila.camargodematos at canonical dot com> ---
Hello,
When recently trying to patch CVE-2023-4806 in glibc for Ubuntu 22.04 LTS, the
Ubuntu Security Team came across a possible regression in version 2.35 that
seems to be related to this bug.
This is the link to the bug report containing more information on the issue
that users came across in Ubuntu 22.04 LTS:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2047155
When patching Ubuntu 22.04's version of glibc (2.35) for CVE-2023-4806 (and
CVEs CVE-2023-4813 and CVE-2023-5156), several of the refactoring commits in
branch release/2.35/master were added as well in order to avoid any possible
issues and simplify the application of the CVE patch (these refactoring commits
are the ones added to sysdeps/posix/getaddrinfo.c in 2023-09). In this group of
commits was commit ce64e72b, which is cherry-picked from e7e5315b, mentioned
here as the cause of the issue in nscd, consequence of a typo in the
refactoring.
Analysis of the release/2.35/master branch seems to indicate that the fix to
this typo was not applied to glibc 2.35, and the report in the Ubuntu Launchpad
bug shows version 2.35 of glibc (more specifically, nscd) being affected by a
regression when previously mentioned refactoring commits are added.
A new version of the Ubuntu 22.04 glibc package will be released and this new
version contains the fix provided in this sourceware bug (commit 227c9035) as
well as three other refactoring commits (backported from the
release/2.36/master branch as well. These are: bc0d18d8, 06890c7b and
d3f2c2c8). Adding these additional changes to the 22.04 glibc 2.35 package seem
to have resolved the issue being reported in the Ubuntu Launchpad bug.
I mention this here in case 2.35 is still being supported, so that the fix to
this issue can be included in that branch as well.
Regards,
Camila Camargo de Matos.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-08 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:19 [Bug nscd/29605] New: " joerg at bec dot de
2022-09-23 12:19 ` [Bug nscd/29605] " fweimer at redhat dot com
2022-09-23 17:55 ` siddhesh at sourceware dot org
2022-09-23 20:22 ` joerg at bec dot de
2022-09-25 11:05 ` holger@applied-asynchrony.com
2022-09-26 13:35 ` siddhesh at sourceware dot org
2022-09-26 17:57 ` siddhesh at sourceware dot org
2022-09-26 18:03 ` sam at gentoo dot org
2022-09-26 18:13 ` holger@applied-asynchrony.com
2022-09-26 18:15 ` sam at gentoo dot org
2022-09-26 19:18 ` holger@applied-asynchrony.com
2022-09-26 19:21 ` siddhesh at sourceware dot org
2022-09-28 16:47 ` cvs-commit at gcc dot gnu.org
2022-09-28 16:48 ` siddhesh at sourceware dot org
2022-09-28 16:49 ` cvs-commit at gcc dot gnu.org
2024-01-08 11:11 ` camila.camargodematos at canonical dot com [this message]
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-29605-131-VA6xE6WWtI@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).