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] vim: correct CVE_PRODUCT mapping
Date: Mon, 24 Aug 2026 04:01:56 -0700 [thread overview]
Message-ID: <20260824110156.25560-1-devanshp@cisco.com> (raw)
From: Devansh Patel <devanshp@cisco.com>
The default "vim" mapping uses a vendor wildcard and also reports the
unrelated JetBrains Vim plugin and VSCodeVim extension.
Use "vim_development_group:vim" for the historical NVD configuration
identity and "vim:vim" for the active NVD dictionary CPE and configuration
identity.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
meta/recipes-support/vim/vim_9.2.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-support/vim/vim_9.2.bb b/meta/recipes-support/vim/vim_9.2.bb
index fee9f055e9..d31d277fae 100644
--- a/meta/recipes-support/vim/vim_9.2.bb
+++ b/meta/recipes-support/vim/vim_9.2.bb
@@ -1,5 +1,7 @@
require vim.inc
+CVE_PRODUCT = "vim_development_group:vim vim:vim"
+
PROVIDES = "xxd"
RDEPENDS:${PN} = "ncurses-terminfo-base ${PN}-xxd"
--
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=20260824110156.25560-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.