From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/{glibc, localedef}: security bump to version 2.43-22-g8362e8ce1
Date: Mon, 04 May 2026 21:23:40 +0200 [thread overview]
Message-ID: <78e69bf08262c04691fa1a2b77d4df39@free.fr> (raw)
In-Reply-To: <20260504184516.356034-1-peter@korsgaard.com>
On 04/05/2026 20:45, Peter Korsgaard wrote:
> Fixes the following security issue:
>
> CVE-2026-4046: iconv crash due to assertion failure with untrusted
> input
>
> https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2026-0007;h=b880fb55449693b879beae443e5d9bc1070b938b;hb=HEAD
>
> git shortlog 2.43-17-gdd9945c0b..2.43-22-g8362e8ce1
> Adhemerval Zanella (1):
> elf: Use dl-symbol-redir-ifunc.h instead _dl_strlen
>
> Adhemerval Zanella Netto (1):
> riscv: Resolve calls to memcpy using memcpy-generic in early
> startup
>
> Florian Weimer (1):
> Use pending character state in IBM1390, IBM1399 character sets
> (CVE-2026-4046)
>
> Michael Jeanson (1):
> tests: fix tst-rseq with Linux 7.0
>
> Xi Ruoyao (1):
> elf: parse /proc/self/maps as the last resort to find the gap for
> tst-link-map-contiguous-ldso
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-05-04 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 18:45 [Buildroot] [PATCH] package/{glibc, localedef}: security bump to version 2.43-22-g8362e8ce1 Peter Korsgaard
2026-05-04 19:23 ` Julien Olivain via buildroot [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=78e69bf08262c04691fa1a2b77d4df39@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=peter@korsgaard.com \
--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