Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)" <devanshp@cisco.com>
To: openembedded-core@lists.openembedded.org
Cc: xe-linux-external@cisco.com
Subject: [OE-core][PATCH] perl: correct CVE_PRODUCT mapping
Date: Wed, 26 Aug 2026 00:53:48 -0700	[thread overview]
Message-ID: <20260826075348.64033-1-devanshp@cisco.com> (raw)

From: Devansh Patel <devanshp@cisco.com>

The default product-only mapping generates a vendor-wildcard CPE.
perl:perl is the active NVD dictionary CPE and configuration identity and
also covers CNA affected data using vendor perl. larry_wall:perl preserves
historical NVD configurations.

leont:perl covers authoritative CNA affected data for the same Perl/perl5
source, including CVE-2026-15534. It has no dictionary record.

This changes the generated identities to three exact CPEs, but the frozen
sbom-cve-check database leaves the 61-entry CVE report unchanged, with no
current CVE delta.

Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
 meta/recipes-devtools/perl/perl_5.44.0.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/perl/perl_5.44.0.bb b/meta/recipes-devtools/perl/perl_5.44.0.bb
index ef76df7e0f..6cf88e7175 100644
--- a/meta/recipes-devtools/perl/perl_5.44.0.bb
+++ b/meta/recipes-devtools/perl/perl_5.44.0.bb
@@ -25,6 +25,8 @@ SRC_URI:append:class-target = " \
 
 SRC_URI[perl.sha256sum] = "3b855066b92491cb40e86affb1ca57d1a388aa43e51b91c7806a32c2f65f96c3"
 
+CVE_PRODUCT = "perl:perl larry_wall:perl leont:perl"
+
 B = "${WORKDIR}/perl-${PV}-build"
 
 inherit upstream-version-is-even update-alternatives upstream-stable-release-point
-- 
2.35.6


                 reply	other threads:[~2026-08-26  7:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260826075348.64033-1-devanshp@cisco.com \
    --to=devanshp@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=xe-linux-external@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox