All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <yurade@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][PATCH 1/2] python3-pyasn1: fix CVE-2026-30922
Date: Fri, 18 Sep 2026 09:39:42 +0200	[thread overview]
Message-ID: <DLI9SJBJS4BF.28AZGGJ901FO@smile.fr> (raw)
In-Reply-To: <20260827063129.3205882-1-yurade@cisco.com>

On Thu Aug 27, 2026 at 8:31 AM CEST, Yogita Urade -X (yurade - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> This patch applies upstream fix for CVE-2026-30922 as referenced in [2],
> using the upstream commit identified in [1].
>
> [1] https://github.com/pyasn1/pyasn1/commit/25ad481c19fdb006e20485ef3fc2e5b3eff30ef0
> [2] https://nvd.nist.gov/vuln/detail/CVE-2026-30922
>
> Signed-off-by: Yogita Urade <yurade@cisco.com>
> ---
>  .../recipes-devtools/python/python-pyasn1.inc |   1 +
>  .../python3-pyasn1/CVE-2026-30922.patch       | 260 ++++++++++++++++++
>  2 files changed, 261 insertions(+)
>  create mode 100644 meta/recipes-devtools/python/python3-pyasn1/CVE-2026-30922.patch
>
> diff --git a/meta/recipes-devtools/python/python-pyasn1.inc b/meta/recipes-devtools/python/python-pyasn1.inc
> index 96b4a3b52a..d69cdf8877 100644
> --- a/meta/recipes-devtools/python/python-pyasn1.inc
> +++ b/meta/recipes-devtools/python/python-pyasn1.inc
> @@ -19,6 +19,7 @@ inherit ptest
>  SRC_URI += " \
>         file://run-ptest \
>         file://CVE-2026-23490.patch \
> +       file://CVE-2026-30922.patch \
>  "
>  
>  RDEPENDS:${PN}-ptest += " \
> diff --git a/meta/recipes-devtools/python/python3-pyasn1/CVE-2026-30922.patch b/meta/recipes-devtools/python/python3-pyasn1/CVE-2026-30922.patch
> new file mode 100644
> index 0000000000..aad4829f82
> --- /dev/null
> +++ b/meta/recipes-devtools/python/python3-pyasn1/CVE-2026-30922.patch
> @@ -0,0 +1,260 @@
> +From b10f9a671c66a99b91bd916e62a0c81541094dd6 Mon Sep 17 00:00:00 2001
> +From: Simon Pichugin <simon.pichugin@gmail.com>
> +Date: Mon, 16 Mar 2026 17:23:11 -0700
> +Subject: [PATCH] Merge commit from fork
> +
> +CVE: CVE-2026-30922
> +Upstream-Status: Backport [https://github.com/pyasn1/pyasn1/commit/25ad481c19fdb006e20485ef3fc2e5b3eff30ef0]
> +
> +(cherry picked from commit 25ad481c19fdb006e20485ef3fc2e5b3eff30ef0)
> +Signed-off-by: Yogita Urade <yurade@cisco.com>
> +---
> + pyasn1/codec/ber/decoder.py     |  10 +++
> + tests/codec/ber/test_decoder.py | 116 ++++++++++++++++++++++++++++++++
> + tests/codec/cer/test_decoder.py |  24 +++++++
> + tests/codec/der/test_decoder.py |  42 ++++++++++++
> + 4 files changed, 192 insertions(+)

Hello,

Thanks for the patch but it does not apply cleanly (surely a conflict
with the other recent CVE fixes):
    ERROR: python3-pyasn1-0.5.1-r0 do_patch: QA Issue: Fuzz detected:

    Applying patch CVE-2026-30922.patch
    patching file pyasn1/codec/ber/decoder.py
    Hunk #1 succeeded at 38 with fuzz 2.
    Hunk #2 succeeded at 1520 (offset 4 lines).
    patching file tests/codec/ber/test_decoder.py
    Hunk #1 succeeded at 2048 (offset 60 lines).
    patching file tests/codec/cer/test_decoder.py
    Hunk #1 succeeded at 389 (offset 25 lines).
    patching file tests/codec/der/test_decoder.py
    Hunk #1 succeeded at 396 (offset 34 lines).

Can you rebase and send a refreshed v2?

Thanks!
-- 
Yoann Congal
Smile ECS



      parent reply	other threads:[~2026-09-18  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  6:31 [OE-core][scarthgap][PATCH 1/2] python3-pyasn1: fix CVE-2026-30922 Yogita Urade
2026-08-27  6:31 ` [OE-core][scarthgap][PATCH 2/2] python3-pyasn1: fix CVE-2026-59885 Yogita Urade
2026-09-18  7:39 ` 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=DLI9SJBJS4BF.28AZGGJ901FO@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yurade@cisco.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 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.