public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: hjadon@cisco.com, openembedded-core@lists.openembedded.org
Cc: vchavda@cisco.com
Subject: Re: [OE-core] [master] [PATCH] acpid2: Add vendor to CVE_PRODUCT
Date: Mon, 13 Apr 2026 13:36:35 +0100	[thread overview]
Message-ID: <15d64fc4f3f3fe599b59afe642d02a0add64b3a5.camel@pbarker.dev> (raw)
In-Reply-To: <20260413111552.1809426-1-hjadon@cisco.com>

[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]

On Mon, 2026-04-13 at 04:15 -0700, Himanshu Jadon -X (hjadon - E
INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> From: Himanshu Jadon <hjadon@cisco.com>
> 
> 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.
> 
> Signed-off-by: Himanshu Jadon <hjadon@cisco.com>
> ---
>  meta/recipes-bsp/acpid/acpid.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-bsp/acpid/acpid.inc b/meta/recipes-bsp/acpid/acpid.inc
> index ba954563b6..0d32249a61 100644
> --- a/meta/recipes-bsp/acpid/acpid.inc
> +++ b/meta/recipes-bsp/acpid/acpid.inc
> @@ -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,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2026-04-13 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 11:15 [OE-core] [master] [PATCH] acpid2: Add vendor to CVE_PRODUCT Himanshu Jadon -X (hjadon - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-04-13 12:36 ` Paul Barker [this message]
2026-04-15  6:16   ` Himanshu Jadon -X (hjadon - 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=15d64fc4f3f3fe599b59afe642d02a0add64b3a5.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=hjadon@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=vchavda@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