All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <UpStream_IP-SP@bmwtechworks.in>,
	<openembedded-core@lists.openembedded.org>
Cc: <souravkumar.pramanik@bmwtechworks.in>
Subject: Re: [OE-core] [scarthgap][PATCHv2 2/2] glibc: Fix CVE-2026-5928
Date: Mon, 12 Oct 2026 23:37:58 +0200	[thread overview]
Message-ID: <DM36NFEVV37N.BP0VL0IXDWR7@smile.fr> (raw)
In-Reply-To: <20261005055601.111500-2-UpStream_IP-SP@bmwtechworks.in>

Hello,

On Mon Oct 5, 2026 at 7:56 AM CEST, Sourav Kumar Pramanik via lists.openembedded.org wrote:
> From: Sourav Kumar Pramanik <souravkumar.pramanik@bmwtechworks.in>
>
> This change fixes CVE-2026-5928
>
> Upstream-Status: Backport [https://sourceware.org/git/?p=glibc.git;a=commit;h=ef3bfb5f910011f3780cb06aa47e730035f53285]
>
> Comment: Patch refreshed as per glibc 2.39 source code
>
> Signed-off-by: Sourav Kumar Pramanik <souravkumar.pramanik@bmwtechworks.in>
> ---
>  .../glibc/glibc/CVE-2026-5928.patch           | 105 ++++++++++++++++++
>  meta/recipes-core/glibc/glibc_2.39.bb         |   1 +
>  2 files changed, 106 insertions(+)
>  create mode 100644 meta/recipes-core/glibc/glibc/CVE-2026-5928.patch

See my review of patch 1/2. It also applies here.

Thanks!
-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-10-12 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  5:56 [scarthgap][PATCHv2 1/2] glibc: Fix CVE-2026-5450 Sourav Kumar Pramanik
2026-10-05  5:56 ` [scarthgap][PATCHv2 2/2] glibc: Fix CVE-2026-5928 Sourav Kumar Pramanik
2026-10-12 21:37   ` Yoann Congal [this message]
2026-10-12 21:35 ` [OE-core] [scarthgap][PATCHv2 1/2] glibc: Fix CVE-2026-5450 Yoann Congal

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=DM36NFEVV37N.BP0VL0IXDWR7@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=UpStream_IP-SP@bmwtechworks.in \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=souravkumar.pramanik@bmwtechworks.in \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.