Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Fabien Thomas" <fabien.thomas@smile.fr>
To: <joaomarcos.costa@bootlin.com>,
	<openembedded-core@lists.openembedded.org>
Cc: <thomas.petazzoni@bootlin.com>
Subject: Re: [OE-core] [scarthgap][PATCH] glibc: fix CVE-2026-84243
Date: Tue, 17 Nov 2026 14:54:34 +0100	[thread overview]
Message-ID: <DMXJC8MY3ICL.3R9DYAAS6OXEF@smile.fr> (raw)
In-Reply-To: <20261104150611.1720587-1-joaomarcos.costa@bootlin.com>

On Wed Nov 4, 2026 at 4:06 PM CET, Joao Marcos Costa via openembedded-core wrote:
> This vulnerability, marked as High [1], was fixed upstream [2] since
> 2.45.
>
> Backport the fix to glibc v2.39.
>
> The only changes not included in the backport are the ones in NEWS file.
>
> [1] https://nvd.nist.gov/vuln/detail/cve-2026-84243
> [2] https://sourceware.org/bugzilla/show_bug.cgi?id=17142
>
> Signed-off-by: João Marcos Costa (Schneider Electric) <joaomarcos.costa@bootlin.com>
> ---
>  .../glibc/glibc/CVE-2026-84243.patch          | 193 ++++++++++++++++++
>  meta/recipes-core/glibc/glibc_2.39.bb         |   1 +
>  2 files changed, 194 insertions(+)
>  create mode 100644 meta/recipes-core/glibc/glibc/CVE-2026-84243.patch
>

Hello João,

Thanks for this patch. However, I can't apply it directly in Scarthgap until
Wrynose branch has been updated, as mentionned in this thread [1].

I'm putting it on hold until then.

[1] https://lore.kernel.org/all/20261112062448.3128219-1-hthakar@cisco.com/
-- 
Fabien Thomas
Smile


      reply	other threads:[~2026-11-17 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 15:06 [scarthgap][PATCH] glibc: fix CVE-2026-84243 João Marcos Costa (Schneider Electric)
2026-11-17 13:54 ` Fabien Thomas [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=DMXJC8MY3ICL.3R9DYAAS6OXEF@smile.fr \
    --to=fabien.thomas@smile.fr \
    --cc=joaomarcos.costa@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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