Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libheif: security bump version to 1.23.1
Date: Sat, 25 Jul 2026 11:46:09 +0200	[thread overview]
Message-ID: <2615844c06fe46a963013c0c4c456f1d@free.fr> (raw)
In-Reply-To: <20260724172124.319019-1-bernd@kuhls.net>

On 24/07/2026 19:21, Bernd Kuhls wrote:
> https://github.com/strukturag/libheif/releases/tag/v1.23.1
> 
> Fixes the following CVEs:
> 
> CVE-2026-62289 (GHSA-jc8f-p23p-5hjg)
> Integer underflow in Fraction constructor via double clap transform
> application
> 
> CVE-2026-62291 (GHSA-xpw3-9rhw-482x)
> Heap out of bounds write in libheif uncompressed encoder when writing
> images with mismatched auxiliary alpha dimensions
> 
> CVE-2026-62292 (GHSA-73p7-m7gg-w2jv)
> Out-of-bounds read in uncompressed unci tile range slicing
> 
> CVE-2026-62377 (GHSA-9ww4-9v47-m7pj)
> Reachable assertion in HeifContext::get_track() aborts on a valid-but-
> empty HEIF sequence file
> 
> (GHSA-46rp-pcq2-rpmr)
> Heap out-of-bounds write in the uncompressed encoder for RRGGBB images
> with interleaved bit-depth ≤ 8
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-07-25  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 17:21 [Buildroot] [PATCH 1/1] package/libheif: security bump version to 1.23.1 Bernd Kuhls
2026-07-25  9:46 ` Julien Olivain via buildroot [this message]
2026-07-31 12:22 ` Thomas Perale via buildroot

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=2615844c06fe46a963013c0c4c456f1d@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=ju.o@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox