From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libslirp: Version bump. 4.9.3 -> 4.9.4
Date: Fri, 18 Sep 2026 11:02:09 +0200 [thread overview]
Message-ID: <20260918090209.1691493-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260904171205.3849412-1-christian.melki@t2data.com>
Thanks, applied as 4df4cd755b6d9b6aa3ecc6fef08bcec12d4f4bc1.
Michael
[sent from post-receive hook]
On Fri, 18 Sep 2026 11:02:09 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Minor changes, security.
> https://gitlab.freedesktop.org/slirp/libslirp/-/blob/v4.9.4/CHANGELOG.md
>
> CVE-2026-9539: oob. Cap urgent data count to what is actually available.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260904171205.3849412-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libslirp.make b/rules/libslirp.make
> index c5ca6aef7e04..1f6a56286883 100644
> --- a/rules/libslirp.make
> +++ b/rules/libslirp.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBSLIRP) += libslirp
> #
> # Paths and names
> #
> -LIBSLIRP_VERSION := 4.9.3
> -LIBSLIRP_SHA256 := c82e22c73bdc3f2c038e538d4f0c9c2166defb2402212d61bb7cb1b530ba952f
> +LIBSLIRP_VERSION := 4.9.4
> +LIBSLIRP_SHA256 := 0ecbac5eebcaa2d59b9d7cf13731f2c9fab80314e4ce31658fe4cf8d8e18102d
> LIBSLIRP := libslirp-v$(LIBSLIRP_VERSION)
> LIBSLIRP_SUFFIX := tar.bz2
> LIBSLIRP_URL := https://gitlab.freedesktop.org/slirp/libslirp/-/archive/v$(LIBSLIRP_VERSION)/$(LIBSLIRP).$(LIBSLIRP_SUFFIX)
prev parent reply other threads:[~2026-09-18 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 17:12 [ptxdist] [PATCH] " Christian Melki
2026-09-18 9:02 ` 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=20260918090209.1691493-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