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] glib-2.0: correct CVE_PRODUCT mapping
Date: Mon, 24 Aug 2026 04:01:57 -0700 [thread overview]
Message-ID: <20260824110157.25841-1-devanshp@cisco.com> (raw)
From: Devansh Patel <devanshp@cisco.com>
The current product-only mapping generates a vendor-wildcard CPE.
gnome:glib is the active NVD dictionary CPE and configuration identity,
and is also used by CNA affected-data records for the packaged GNOME
GLib source.
This changes the generated product identity. With the frozen
sbom-cve-check database, the 35-entry CVE report is unchanged, so this is
an identity correction with no CVE delta.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
meta/recipes-core/glib-2.0/glib-2.0_2.88.3.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.88.3.bb b/meta/recipes-core/glib-2.0/glib-2.0_2.88.3.bb
index ef80cc47cf..f401ea9c23 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0_2.88.3.bb
+++ b/meta/recipes-core/glib-2.0/glib-2.0_2.88.3.bb
@@ -1,2 +1,3 @@
require glib.inc
+CVE_PRODUCT = "gnome:glib"
--
2.35.6
reply other threads:[~2026-08-24 11:02 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=20260824110157.25841-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.