mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] expat: Version bump. 2.8.3 -> 2.8.4
Date: Fri, 18 Sep 2026 11:02:11 +0200	[thread overview]
Message-ID: <20260918090211.1691575-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260904173847.4107208-1-christian.melki@t2data.com>

Thanks, applied as 3e7be1ffb82fab390d046047f21125c6dcbcb882.

Michael

[sent from post-receive hook]

On Fri, 18 Sep 2026 11:02:11 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Security fixes.
> https://github.com/libexpat/libexpat/blob/R_2_8_4/expat/Changes
> 
> CVE-2026-66046: Fix quadratic runtime.
> CVE-2026-76641: Fix quadratic runtime.
> CVE-2026-76957: Protect custom encoding callbacks from parser re-entry.
> CVE-2026-76956: Fix inverted getentropy() return handling.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260904173847.4107208-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/expat.make b/rules/expat.make
> index 767da98b9d63..598f870d3093 100644
> --- a/rules/expat.make
> +++ b/rules/expat.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_EXPAT) += expat
>  #
>  # Paths and names
>  #
> -EXPAT_VERSION		:= 2.8.3
> -EXPAT_SHA256		:= b4cc2483927d5e90bf8c40b44a6b95b368b42a8a96e25883fce188b48a92b670
> +EXPAT_VERSION		:= 2.8.4
> +EXPAT_SHA256		:= 963250a823c16a498582b4ad82ad0f88926be0769675d3b6956be4d769a1cd8f
>  EXPAT			:= expat-$(EXPAT_VERSION)
>  EXPAT_SUFFIX		:= tar.bz2
>  EXPAT_RELEASE		:= R_$(subst .,_,$(EXPAT_VERSION))



      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:38 [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=20260918090211.1691575-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