From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Romain Naour <romain.naour@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH-2024.02.x] package/glibc: security bump to 2.38-81 for post-2.38 security fixes
Date: Mon, 17 Jun 2024 07:54:31 +0200 [thread overview]
Message-ID: <87jziop10o.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <Zm9OZq0a8stlLLKh@landeda> (Yann E. MORIN's message of "Sun, 16 Jun 2024 22:43:18 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Peter, All,
> On 2024-06-16 16:20 +0200, Peter Korsgaard spake thusly:
>> Fixes the following security issues:
>>
>> GLIBC-SA-2024-0004:
>> ISO-2022-CN-EXT: fix out-of-bound writes when writing escape
>> sequence (CVE-2024-2961)
>>
>> GLIBC-SA-2024-0005:
>> nscd: Stack-based buffer overflow in netgroup cache (CVE-2024-33599)
>>
>> GLIBC-SA-2024-0006:
>> nscd: Null pointer crash after notfound response (CVE-2024-33600)
>>
>> GLIBC-SA-2024-0007:
>> nscd: netgroup cache may terminate daemon on memory allocation
>> failure (CVE-2024-33601)
>>
>> GLIBC-SA-2024-0008:
>> nscd: netgroup cache assumes NSS callback uses in-buffer strings
>> (CVE-2024-33602)
>>
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> Reviewed-by: Yann E. MORIN <yann.morin.1998@free.fr>
Committed to 2024.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-06-17 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 14:20 [Buildroot] [PATCH-2024.02.x] package/glibc: security bump to 2.38-81 for post-2.38 security fixes Peter Korsgaard
2024-06-16 20:43 ` Yann E. MORIN
2024-06-17 5:54 ` Peter Korsgaard [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=87jziop10o.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.