From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sebastian Weyer <sebastian.weyer@smile.fr>, buildroot@buildroot.org
Cc: James Hilliard <james.hilliard1@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Romain Naour <romain.naour@smile.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/glibc: bump to version 2.37
Date: Sat, 8 Apr 2023 09:36:11 +0700 [thread overview]
Message-ID: <ZDDTG7pp7KsrClHE@debian.me> (raw)
In-Reply-To: <20230329193028.775041-1-sebastian.weyer@smile.fr>
[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]
On Wed, Mar 29, 2023 at 09:30:27PM +0200, Sebastian Weyer wrote:
> From: Romain Naour <romain.naour@smile.fr>
>
> See:
> https://sourceware.org/glibc/wiki/Release/2.37
> https://lists.gnu.org/archive/html/info-gnu/2023-02/msg00000.html
>
> Security related changes:
>
> CVE-2022-39046: When the syslog function is passed a crafted input
> string larger than 1024 bytes, it reads uninitialized memory from the
> heap and prints it to the target log file, potentially revealing a
> portion of the contents of the heap
>
> Remove patch 0001-Revert-Linux-Implement-a-useful-version-of-_startup_.patch fixed
> in 2.37 release by [1].
>
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=29249
>
ping?
Or has this been applied?
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-04-08 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 19:30 [Buildroot] [PATCH 1/1] package/glibc: bump to version 2.37 Sebastian Weyer
2023-04-02 12:58 ` Bagas Sanjaya
2023-04-08 2:36 ` Bagas Sanjaya [this message]
2023-04-10 19:27 ` Yann E. MORIN
2023-04-11 11:31 ` yann.morin
2023-04-11 20:33 ` Yann E. MORIN
2023-04-12 8:17 ` Sebastian WEYER
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=ZDDTG7pp7KsrClHE@debian.me \
--to=bagasdotme@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=sebastian.weyer@smile.fr \
--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 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.