Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libheif: security bump version to 1.23.1
Date: Fri, 31 Jul 2026 14:22:05 +0200	[thread overview]
Message-ID: <20260731122205.155827-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260724172124.319019-1-bernd@kuhls.net>

In reply of:
> 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 2025.02.x & 2026.05.x. Thanks

> ---
> Gitlab pipelines passed:
> https://gitlab.com/bkuhls/buildroot/-/commits/a3d9028ad1a824e62d3a0a573ceca7c79addeebd
> 
>  package/libheif/libheif.hash | 4 ++--
>  package/libheif/libheif.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/libheif/libheif.hash b/package/libheif/libheif.hash
> index 780059facf..ff8c05c7e4 100644
> --- a/package/libheif/libheif.hash
> +++ b/package/libheif/libheif.hash
> @@ -1,4 +1,4 @@
> -# From https://github.com/strukturag/libheif/releases/tag/v1.23.0
> -sha256  4c9182b18897617182eed12ab5eb9f9d855b3aa3a736d6bdb31abc034ec7d393  libheif-1.23.0.tar.gz
> +# From https://github.com/strukturag/libheif/releases/tag/v1.23.1
> +sha256  0de0327f60fcd47de90d5654c6fe152232738d60d84fe084ec3e0f35e03b166a  libheif-1.23.1.tar.gz
>  # Locally computed:
>  sha256  fa81ce652315b013359d6e8e4744335f31a50c7c192907176d3632f78a3b4596  COPYING
> diff --git a/package/libheif/libheif.mk b/package/libheif/libheif.mk
> index be97b18bd0..124dba7c24 100644
> --- a/package/libheif/libheif.mk
> +++ b/package/libheif/libheif.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -LIBHEIF_VERSION = 1.23.0
> +LIBHEIF_VERSION = 1.23.1
>  LIBHEIF_SITE = https://github.com/strukturag/libheif/releases/download/v$(LIBHEIF_VERSION)
>  LIBHEIF_LICENSE = LGPL-3.0+
>  LIBHEIF_LICENSE_FILES = COPYING
> -- 
> 2.47.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-07-31 12:22 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
2026-07-31 12:22 ` Thomas Perale 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=20260731122205.155827-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=thomas.perale@mind.be \
    /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