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 v2] u-boot: share CVE_PRODUCT with u-boot-tools
Date: Mon, 24 Aug 2026 10:07:12 -0700 [thread overview]
Message-ID: <20260824170712.64140-1-devanshp@cisco.com> (raw)
In-Reply-To: <20260824110158.26007-1-devanshp@cisco.com>
From: Devansh Patel <devanshp@cisco.com>
u-boot-tools builds host utilities from the same source as u-boot, but it
does not inherit the existing CVE_PRODUCT assignment and falls back to its
unrecognized recipe-name identity. Move the mapping to u-boot-common.inc
so both recipes inherit it.
Use "u-boot:u-boot" for the CNA/CVE List V5 affected-data identity and
"denx:u-boot" for the NVD dictionary CPE and configuration identity. The
CNA records are also covered by NVD today, but retaining both authoritative
identities permits direct matching independently of NVD enrichment.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
meta/recipes-bsp/u-boot/u-boot-common.inc | 2 ++
meta/recipes-bsp/u-boot/u-boot.inc | 2 --
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common.inc b/meta/recipes-bsp/u-boot/u-boot-common.inc
index d82d42cbce..86c4fed2bc 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common.inc
@@ -10,6 +10,8 @@ LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://Licenses/README;md5=2ca5f2c35c8cc335f0a19756634782f1"
PE = "1"
+CVE_PRODUCT = "u-boot:u-boot denx:u-boot"
+
# We use the revision in order to avoid having to fetch it from the
# repo during parse
SRCREV = "ece349ade2973e220f524ce59e59711cc919263f"
diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc
index 2197039dbc..b9f61a185c 100644
--- a/meta/recipes-bsp/u-boot/u-boot.inc
+++ b/meta/recipes-bsp/u-boot/u-boot.inc
@@ -21,8 +21,6 @@ PACKAGECONFIG ??= "openssl"
# a host build dependency.
PACKAGECONFIG[openssl] = ",,openssl-native"
-CVE_PRODUCT = "denx:u-boot"
-
# Allow setting an additional version string that will be picked up by the
# u-boot build system and appended to the u-boot version. If the .scmversion
# file already exists it will not be overwritten.
--
2.35.6
prev parent reply other threads:[~2026-08-24 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 11:01 [OE-core][PATCH] u-boot-tools: add CVE_PRODUCT mapping Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-08-24 11:08 ` Quentin Schulz
2026-08-24 13:24 ` [PATCH] " Devansh Patel
2026-08-24 17:10 ` Devansh Patel
2026-08-24 17:07 ` Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
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=20260824170712.64140-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