From: mark.yang@lge.com
To: openembedded-devel@lists.openembedded.org
Cc: "mark.yang" <mark.yang@lge.com>
Subject: [meta-python][PATCH 1/2] python3-aiodns: set CVE_PRODUCT and set status for CVE-2025-48945
Date: Wed, 22 Jul 2026 15:09:34 +0900 [thread overview]
Message-ID: <20260722060935.273232-1-mark.yang@lge.com> (raw)
From: "mark.yang" <mark.yang@lge.com>
The pypi class default python:aiodns doesn't match how aiodns is
tracked in the CVE databases. NVD has no CPE for aiodns yet; the only
existing record (CVE-2025-48945) carries aio-libs:aiodns in its CNA
affected entry [1], so set that pair.
CVE-2025-48945 itself is a use-after-free in pycares: the GHSA lives
in the pycares repository [2] and the affected range "< 4.9.0" uses
pycares version numbers (fixed in pycares 4.9.0 [3], we ship 5.0.1).
Mark it cpe-incorrect so it doesn't get reported against aiodns.
[1] https://www.cve.org/CVERecord?id=CVE-2025-48945
[2] https://github.com/saghul/pycares/security/advisories/GHSA-5qpg-rh4j-qp35
[3] https://github.com/saghul/pycares/releases/tag/v4.9.0
Signed-off-by: mark.yang <mark.yang@lge.com>
---
meta-python/recipes-devtools/python/python3-aiodns_4.0.4.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta-python/recipes-devtools/python/python3-aiodns_4.0.4.bb b/meta-python/recipes-devtools/python/python3-aiodns_4.0.4.bb
index 875ec724d3..eb66cc5f34 100644
--- a/meta-python/recipes-devtools/python/python3-aiodns_4.0.4.bb
+++ b/meta-python/recipes-devtools/python/python3-aiodns_4.0.4.bb
@@ -15,4 +15,7 @@ RDEPENDS:${PN} += " \
python3-pycares \
"
+CVE_PRODUCT = "aio-libs:aiodns"
+CVE_STATUS[CVE-2025-48945] = "cpe-incorrect: this CVE is for pycares, fixed in pycares 4.9.0"
+
BBCLASSEXTEND = "native nativesdk"
next reply other threads:[~2026-07-22 6:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 6:09 mark.yang [this message]
2026-07-22 6:09 ` [meta-python][PATCH 2/2] python3-h11: set CVE_PRODUCT mark.yang
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=20260722060935.273232-1-mark.yang@lge.com \
--to=mark.yang@lge.com \
--cc=openembedded-devel@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