Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <SaiSireesha.T@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Cc: <Randy.MacLeod@windriver.com>
Subject: Re: [OE-core] [wrynose][PATCH] libsoup: fix CVE-2026-0719
Date: Sat, 14 Nov 2026 14:48:47 +0100	[thread overview]
Message-ID: <DMUZC6JXWO2M.39O0FWABUZ5HY@smile.fr> (raw)
In-Reply-To: <20261106160329.86073-1-saisireesha.t@windriver.com>

On Fri Nov 6, 2026 at 5:03 PM CET, Sai Sireesha via openembedded-core T wrote:
> Stack-based buffer overflow in the NTLM authentication module when
> handling excessively long passwords.
>
> Backport from [1].
>
> [1] https://github.com/GNOME/libsoup/commit/1972635264f1d9ab1823c8b6becf921b4125b513
>
> Signed-off-by: Sai Sireesha T <saisireesha.t@windriver.com>
> ---
>  .../libsoup/libsoup/CVE-2026-0719.patch       | 191 ++++++++++++++++++
>  meta/recipes-support/libsoup/libsoup_3.6.6.bb |   1 +
>  2 files changed, 192 insertions(+)
>  create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2026-0719.patch

Hello,

I think master is fine for this CVE (3.8.1, with the CVE status you
sent). But blacksail (at 3.6.6, like wrynose) is not fixed and need a
fix as well.

Please add an explanation as to why you think this is the patch to
backport to fix the CVE. Look at a few CVE fixes on the stable branches
to see what I expect.

Thanks!
-- 
Yoann Congal
Smile ECS


      reply	other threads:[~2026-11-14 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 16:03 [wrynose][PATCH] libsoup: fix CVE-2026-0719 Sai Sireesha T
2026-11-14 13:48 ` 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=DMUZC6JXWO2M.39O0FWABUZ5HY@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=Randy.MacLeod@windriver.com \
    --cc=SaiSireesha.T@windriver.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