Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <dkelaiya@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][wrynose][PATCH 3/3] python3: fix CVE-2026-87910
Date: Sat, 14 Nov 2026 10:42:37 +0100	[thread overview]
Message-ID: <DMUU3P3KWKLT.308M5CKOHWEOP@smile.fr> (raw)
In-Reply-To: <20261016053944.3835603-4-dkelaiya@cisco.com>

On Fri Oct 16, 2026 at 7:39 AM CEST, Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> From: Darsh Kelaiya <dkelaiya@cisco.com>
>
> This patch applies the upstream fix shown in [1]. The Windows test
> correction is applied from [2]. The advisory identifying the fix is
> referenced in [3].
>
> [1] https://github.com/python/cpython/commit/fb2f0bbc3b35264f09cc2cb2934b7987527a6bc2
> [2] https://github.com/python/cpython/commit/d9565e54b1fc6d63c5be9afd58114499128fa57b
> [3] https://nvd.nist.gov/vuln/detail/cve-2026-87910
>
> Signed-off-by: Darsh Kelaiya <dkelaiya@cisco.com>
> ---
>  .../python/python3/CVE-2026-87910_p1.patch    | 98 +++++++++++++++++++

Hello,

CVE-2026-87910_p1.patch now fails to apply on top of the recent python3
upgrade:
| ERROR: python3-3.14.10-r0 do_patch: Applying patch 'wrynose/_review/worktrees/openembedded-core/meta/recipes-devtools/python/python3/CVE-2026-87910_p1.patch' on target directory 'bitbake-builds/wrynose/tmp/work/x86-64-v3-oe-linux/python3/3.14.10/sources/Python-3.14.10'
| CmdError('quilt --quiltrc bitbake-builds/wrynose/tmp/work/x86-64-v3-oe-linux/python3/3.14.10/recipe-sysroot-native/etc/quiltrc push', 0, 'stdout: Applying patch CVE-2026-87910_p1.patch
| patching file Lib/tarfile.py
| Hunk #1 FAILED at 2818.
| 1 out of 1 hunk FAILED -- rejects in file Lib/tarfile.py
| patching file Lib/test/test_tarfile.py
| Hunk #1 FAILED at 4395.
| Hunk #2 succeeded at 4710 with fuzz 2 (offset 134 lines).
| 1 out of 2 hunks FAILED -- rejects in file Lib/test/test_tarfile.py
| patching file Misc/NEWS.d/next/Security/2026-09-10-13-38-11.gh-issue-157265.-vYuMp.rst
| Patch CVE-2026-87910_p1.patch does not apply (enforce with -f)

Can you rebase&resend?

Thanks!
-- 
Yoann Congal
Smile ECS


  reply	other threads:[~2026-11-14  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  5:39 [Internal Review][OE-core][wrynose][PATCH 0/3] python3: upgrade to 3.14.8 and backport security fixes Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-16  5:39 ` [OE-core][wrynose][PATCH 1/3] python3: upgrade 3.14.7 -> 3.14.8 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-19 14:18   ` Yoann Congal
2026-10-16  5:39 ` [OE-core][wrynose][PATCH 2/3] python3: fix CVE-2025-15367 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-16  5:39 ` [OE-core][wrynose][PATCH 3/3] python3: fix CVE-2026-87910 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-14  9:42   ` Yoann Congal [this message]
2026-11-17 12:51     ` [wrynose][PATCH " Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-16  5:54 ` [OE-core][wrynose][PATCH 0/3] python3: upgrade to 3.14.8 and backport security fixes Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)

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=DMUU3P3KWKLT.308M5CKOHWEOP@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=dkelaiya@cisco.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