Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <jason.stasiak@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [scarthgap][PATCH] libsoup-2.4: fix CVE-2026-1467
Date: Fri, 30 Oct 2026 19:14:16 +0100	[thread overview]
Message-ID: <DMIDL9WPJ77U.C0WBAFUQBDSV@smile.fr> (raw)
In-Reply-To: <20260831211324.635049-1-jason.stasiak@garmin.com>

On Mon Aug 31, 2026 at 11:13 PM CEST, Jason Stasiak via lists.openembedded.org wrote:
> From: Jason Stasiak <jason.stasiak@gmail.com>
>
> Backport fix for CVE-2026-1467 from meta-oe to OE-core.
> Update CVE patch to address a use case where a uri validation
> failure was not handled.
>
> (From meta-oe rev: 07d67228162018f5f619dce7183f85e79293378d)
>
> Signed-off-by: Jason Stasiak <jason.stasiak@gmail.com>
> ---
>  .../libsoup/libsoup-2.4/CVE-2026-1467.patch   | 276 ++++++++++++++++++
>  .../libsoup/libsoup-2.4_2.74.3.bb             |   1 +
>  2 files changed, 277 insertions(+)
>  create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2026-1467.patch

Hello,

Sorry I took so much time answering this one. It has some non-trivial
changes from upstream and I pushed its review "for later" for 2 months
now :-/

Since you have another series on libsoup-2.4[0], can you merge this CVE fix
into its next version? ... and also applying the same review as the
series:
* metadata preservation (authorship, subject, ...)
* diff minimisation from upstream patch

[0]: https://lore.kernel.org/all/20261014161209.2227316-1-jason.stasiak@garmin.com/

Thanks!
-- 
Yoann Congal
Smile ECS


      parent reply	other threads:[~2026-10-30 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 21:13 [scarthgap][PATCH] libsoup-2.4: fix CVE-2026-1467 Jason Stasiak
2026-09-01  8:32 ` [OE-core] " Yoann Congal
2026-09-01 14:35   ` Jason
2026-09-01 14:37     ` Yoann Congal
2026-10-30 18:14 ` Yoann Congal [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=DMIDL9WPJ77U.C0WBAFUQBDSV@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=jason.stasiak@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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