From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] sdl2-image: Version bump. 2.8.8 -> 2.8.12
Date: Fri, 4 Sep 2026 08:53:02 +0200 [thread overview]
Message-ID: <20260904065302.11014-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260819180301.3409314-1-christian.melki@t2data.com>
Thanks, applied as 9c0b158e4fa4ed82a0677e38e372202879303cf7.
Michael
[sent from post-receive hook]
On Fri, 04 Sep 2026 08:53:02 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> https://github.com/libsdl-org/SDL_image/releases/tag/release-2.8.10
> https://github.com/libsdl-org/SDL_image/releases/tag/release-2.8.12
>
> Plugs CVE:
> CVE-2026-35444: Fixed out of bounds read in XCF image loader
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260819180301.3409314-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/sdl2-image.make b/rules/sdl2-image.make
> index 84a0a1f4444d..156fc228bca1 100644
> --- a/rules/sdl2-image.make
> +++ b/rules/sdl2-image.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_SDL2_IMAGE) += sdl2-image
> #
> # Paths and names
> #
> -SDL2_IMAGE_VERSION := 2.8.8
> -SDL2_IMAGE_SHA256 := 2213b56fdaff2220d0e38c8e420cbe1a83c87374190cba8c70af2156097ce30a
> +SDL2_IMAGE_VERSION := 2.8.12
> +SDL2_IMAGE_SHA256 := 393f5efb50536ec13ca4f4affb69cc9966d3c3f969e6c5e701faddf9f9785381
> SDL2_IMAGE := SDL2_image-$(SDL2_IMAGE_VERSION)
> SDL2_IMAGE_SUFFIX := tar.gz
> SDL2_IMAGE_URL := https://github.com/libsdl-org/SDL_image/releases/download/release-$(SDL2_IMAGE_VERSION)/$(SDL2_IMAGE).$(SDL2_IMAGE_SUFFIX)
prev parent reply other threads:[~2026-09-04 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 18:03 [ptxdist] [PATCH] " Christian Melki
2026-09-04 6:53 ` Michael Olbrich [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=20260904065302.11014-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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