Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: devanshp@cisco.com, openembedded-core@lists.openembedded.org
Cc: xe-linux-external@cisco.com
Subject: Re: [OE-core][PATCH] u-boot-tools: add CVE_PRODUCT mapping
Date: Mon, 24 Aug 2026 13:08:11 +0200	[thread overview]
Message-ID: <683e7f3c-9107-40cd-aadd-975cdd2a64f7@cherry.de> (raw)
In-Reply-To: <20260824110158.26007-1-devanshp@cisco.com>

Hi Devansh,

On 8/24/26 1:01 PM, Devansh Patel via lists.openembedded.org wrote:
> From: Devansh Patel <devanshp@cisco.com>
> 
> The current inherited "u-boot-tools" identity has no vulnerability records even
> though this recipe builds host utilities from the U-Boot source tree, so
> source-aligned CVEs are missed.
> 
> Use "u-boot:u-boot" for the CNA affected-data identity and
> "denx:u-boot" for the NVD dictionary CPE and configuration identity.
> 

How about using a file that is included by both u-boot-tools and u-boot 
so that we don't have to not forget to update both?

u-boot-common.inc is included by both u-boot-tools.bb and u-boot.bb so 
that seems like an ideal candidate (if so, then we probably could remove 
CVE_PRODUCT from u-boot.inc?)

We only have denx:u-boot today in u-boot.inc, how did you come to the 
conclusion we also needed u-boot:u-boot?

Cheers,
Quentin


  reply	other threads:[~2026-08-24 11:08 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 [this message]
2026-08-24 13:24   ` [PATCH] " Devansh Patel
2026-08-24 17:10     ` Devansh Patel
2026-08-24 17:07 ` [OE-core][PATCH v2] u-boot: share CVE_PRODUCT with u-boot-tools Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)

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=683e7f3c-9107-40cd-aadd-975cdd2a64f7@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=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