From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] glib: Version bump. 2.86.3 -> 2.86.4
Date: Mon, 2 Mar 2026 10:25:21 +0100 [thread overview]
Message-ID: <20260302092521.3502435-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260215114439.3245026-1-christian.melki@t2data.com>
Thanks, applied as bc1fcc8ba0bb4cf68072490690fc9c7784d6cb76.
Michael
[sent from post-receive hook]
On Mon, 02 Mar 2026 10:25:21 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Bugfix, security release.
> https://gitlab.gnome.org/GNOME/glib/-/releases/2.86.4
>
> Plugs CVEs:
> CVE-2026-1484 - Buffer underflow on Glib through glib/gbase64.c via g_base64_encode_close()
> CVE-2026-1485 - Buffer underflow on Glib through gio/gcontenttype-fdo.c via parse_header()
> CVE-2026-1489 - Integer Overflow on Glib through glib/guniprop.c via output_marks()
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260215114439.3245026-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/glib.make b/rules/glib.make
> index 340987a7ef20..1013c5e41392 100644
> --- a/rules/glib.make
> +++ b/rules/glib.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_GLIB) += glib
> #
> # Paths and names
> #
> -GLIB_VERSION := 2.86.3
> -GLIB_MD5 := 2383dcdbf3eeb35d9ab005532fb256ba
> +GLIB_VERSION := 2.86.4
> +GLIB_MD5 := f2233a826c952aaae42b4a61611a06a4
> GLIB := glib-$(GLIB_VERSION)
> GLIB_SUFFIX := tar.xz
> GLIB_URL := $(call ptx/mirror, GNOME, glib/$(basename $(GLIB_VERSION))/$(GLIB).$(GLIB_SUFFIX))
prev parent reply other threads:[~2026-03-02 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 11:44 [ptxdist] [PATCH] " Christian Melki
2026-03-02 9:25 ` 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=20260302092521.3502435-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