From: mark.yang@lge.com
To: openembedded-core@lists.openembedded.org
Cc: "mark.yang" <mark.yang@lge.com>
Subject: [PATCH 3/4] python3-pyasn1: set CVE_PRODUCT
Date: Fri, 10 Jul 2026 16:43:03 +0900 [thread overview]
Message-ID: <20260710074415.3341616-3-mark.yang@lge.com> (raw)
In-Reply-To: <20260710074415.3341616-1-mark.yang@lge.com>
From: "mark.yang" <mark.yang@lge.com>
Set the product to pyasn1.
The default python:pyasn1 does not match the NVD/CNA entries which use pyasn1 as vendor, so CVEs like CVE-2026-30922
are never reported.
Signed-off-by: mark.yang <mark.yang@lge.com>
---
meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb b/meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb
index fb572d9da4..ee3cfc9813 100644
--- a/meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb
+++ b/meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb
@@ -14,4 +14,6 @@ RDEPENDS:${PN}:class-target += " \
python3-shell \
"
+CVE_PRODUCT = "pyasn1"
+
BBCLASSEXTEND = "native nativesdk"
next prev parent reply other threads:[~2026-07-10 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:43 [PATCH 1/4] python3-cryptography: set CVE_PRODUCT mark.yang
2026-07-10 7:43 ` [PATCH 2/4] python3-ply: set CVE_PRODUCT and CVE_STATUS for CVE-2025-56005 as disputed mark.yang
2026-07-13 16:24 ` [OE-core] " Paul Barker
2026-07-10 7:43 ` mark.yang [this message]
2026-07-13 17:14 ` [OE-core] [PATCH 3/4] python3-pyasn1: set CVE_PRODUCT Ross Burton
2026-07-10 7:43 ` [PATCH 4/4] libx11-compose-data: set CVE_PRODUCT to empty value mark.yang
2026-07-13 17:15 ` [OE-core] [PATCH 1/4] python3-cryptography: set CVE_PRODUCT Ross Burton
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=20260710074415.3341616-3-mark.yang@lge.com \
--to=mark.yang@lge.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