acpid2: Add vendor to CVE_PRODUCT
PATCH 1/1 acpid2: Add vendor to CVE_PRODUCT
From: Himanshu Jadon <[email protected]>
Added tedfelix as a vendor to CVE_PRODUCT to align with the product naming defined in the NVD CPE database for acpid2.
Only a single CPE entry exists in the NVD for this product:
cpe:2.3:a:tedfelix:acpid2
So far, only two CVEs have been reported against this CPE, confirming it as the correct mapping for CVE reporting.
--- meta/recipes-bsp/acpid/acpid.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-bsp/acpid/acpid.inc +1 -1
@@ -17,7 +17,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/${SOURCEFORGE_PROJECT}/acpid-${PV}.tar.xz \ file://0001-Replace-stat64-with-stat.patch \ " -CVE_PRODUCT = "acpid2" +CVE_PRODUCT = "tedfelix:acpid2" inherit autotools update-rc.d systemd sourceforge-releases
Signature · 1 line
2.35.6
Quoted 21 lines · On Mon, 2026-04-13 at 04:15 -0700, Himanshu Jadon -X (hjadon - E INFOCHIPS…
From: Himanshu Jadon <[email protected]>
Added
tedfelixas a vendor toCVE_PRODUCTto align with the product naming defined in the NVD CPE database foracpid2.Only a single CPE entry exists in the NVD for this product:
cpe:2.3:a:tedfelix:acpid2So far, only two CVEs have been reported against this CPE, confirming it as the correct mapping for CVE reporting.
Signed-off-by Himanshu Jadon <[email protected]>--- meta/recipes-bsp/acpid/acpid.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-bsp/acpid/acpid.inc +0
-0
meta/recipes-bsp/acpid/acpid.inc SRC_URI = "${SOURCEFORGE_MIRROR}/${SOURCEFORGE_PROJECT}/acpid-${PV}.tar.xz \ · line 20
Quoted 5 lines
meta/recipes-bsp/acpid/acpid.inc +1
-1@@ -17,7 +17,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/${SOURCEFORGE_PROJECT}/acpid-${PV}.tar.xz \ file://0001-Replace-stat64-with-stat.patch \ " -CVE_PRODUCT = "acpid2" +CVE_PRODUCT = "tedfelix:acpid2"
I don't see any other invalid CPEs when I search for "acpid2" [1]. Why do we need to specify the vendor here? Are you seeing matches against other CPEs for acpid2?
[1]: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=acpid2
Best regards,
Signature · 1 line
Paul Barker
Hi,
Thanks for checking this.
You are right, at present there is only one valid CPE for acpid2 (tedfelix:acpid2), and we are not seeing any wrong matches against other CPEs right now.
This update is mainly to make the mapping explicit, instead of depending on product-only implicit matching. As of now, it does not change current CVE reporting output. The intent is to keep mapping stable if matching logic changes later, or if NVD adds another vendor:product using the same product token in future.
So this is a proactive metadata clarity change, not a fix for any current misreporting.