python3-cryptography: set CVE_PRODUCT
PATCH v2 1/4 python3-cryptography: set CVE_PRODUCT
From: "mark.yang" <[email protected]>
NVD lists it as cryptography.io:cryptography and CNA lists it as pyca:cryptography, so set both vendor:product pairs to match correctly and precisely.
---
v2: use explicit vendor:product list
meta/recipes-devtools/python/python3-cryptography.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-devtools/python/python3-cryptography.bb +2 -0
@@ -71,4 +71,6 @@ do_install_ptest() { cp -r ${S}/pyproject.toml ${D}${PTEST_PATH}/ } +CVE_PRODUCT = "cryptography.io:cryptography pyca:cryptography" + BBCLASSEXTEND = "native nativesdk"
PATCH v2 2/4 python3-ply: set CVE_PRODUCT
From: "mark.yang" <[email protected]>
NVD registers ply as dabeaz:ply, so the default python:ply vendor prefix never matches and no CVEs are reported. Use the exact vendor:product pair.
CVE-2025-56005 will then show as unpatched; no fixed release exists.
---
v2: use exact vendor:product pair; drop CVE_STATUS
meta/recipes-devtools/python/python3-ply_3.11.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-devtools/python/python3-ply_3.11.bb +2 -0
@@ -14,4 +14,6 @@ RDEPENDS:${PN}:class-target += "\ python3-shell \ " +CVE_PRODUCT = "dabeaz:ply" + BBCLASSEXTEND = "native nativesdk"
PATCH v2 3/4 python3-pyasn1: set CVE_PRODUCT
In reply to [email protected]From: "mark.yang" <[email protected]>
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. Use the exact pyasn1:pyasn1 pair.
---
v2: use exact vendor:product pair
meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb +2 -0
@@ -14,4 +14,6 @@ RDEPENDS:${PN}:class-target += " \ python3-shell \ " +CVE_PRODUCT = "pyasn1:pyasn1" + BBCLASSEXTEND = "native nativesdk"
PATCH v2 4/4 libx11-compose-data: set CVE_PRODUCT to empty value
In reply to [email protected]From: "mark.yang" <[email protected]>
This recipe only builds and installs the compose data files (nls/) from the libX11 sources and contains no compiled libX11 code, so libx11 CVEs do not apply to it. When the x11 DISTRO_FEATURE is enabled this recipe is skipped and libx11 itself is built and scanned instead.
Referred glibc-locale case:
https://github.com/openembedded/openembedded-core/commit/1f9a963b9ff7ebe052ba54b9fcbdf7d09478dd17
---
v2: no changes
.../recipes-graphics/xorg-lib/libx11-compose-data_1.8.12.bb | 6 ++++++ 1 file changed, 6 insertions(+)
meta/recipes-graphics/xorg-lib/libx11-compose-data_1.8.12.bb +6 -0
@@ -29,3 +29,9 @@ do_install() { PACKAGES = "${PN}" FILES:${PN} = "${datadir}/X11/locale ${libdir}/X11/locale" + +# This recipe only builds and installs the compose data files (nls/) from +# the libX11 sources and contains no compiled libX11 code, so libx11 CVEs +# do not apply to it. When the x11 DISTRO_FEATURE is enabled this recipe +# is skipped and libx11 itself is built and scanned instead. +CVE_PRODUCT = ""