Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Romain Naour <romain.naour@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH-2023.02.x] package/{glibc, localedef}: security bump to version glibc-2.36-128-gb9b7d6a27aa0632f334352fa400771115b3c69b7
Date: Tue, 06 Feb 2024 18:30:56 +0100	[thread overview]
Message-ID: <87mssd5wkv.fsf@48ers.dk> (raw)
In-Reply-To: <20240131111301.497468-1-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 31 Jan 2024 12:13:01 +0100")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes the following security issues:
 > CVE-2023-6246: syslog: Fix heap buffer overflow in __vsyslog_internal
 > https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2024-0001;hb=HEAD

 > CVE-2023-6779: syslog: Heap buffer overflow in __vsyslog_internal
 > https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2024-0002;hb=HEAD

 > CVE-2023-6780: syslog: Integer overflow in __vsyslog_internal
 > https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2024-0003;hb=HEAD

 > For details, see the Qualys advisory:
 > https://www.openwall.com/lists/oss-security/2024/01/30/6

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2023.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-02-06 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 11:13 [Buildroot] [PATCH-2023.02.x] package/{glibc, localedef}: security bump to version glibc-2.36-128-gb9b7d6a27aa0632f334352fa400771115b3c69b7 Peter Korsgaard
2024-02-06 17:30 ` 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=87mssd5wkv.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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