From: "Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)" <devanshp@cisco.com>
To: meta-virtualization@lists.yoctoproject.org
Cc: xe-linux-external@cisco.com
Subject: [meta-virtualization][PATCH] podman: correct CVE_PRODUCT mapping
Date: Thu, 20 Aug 2026 22:07:09 -0700 [thread overview]
Message-ID: <20260821050709.49931-1-devanshp@cisco.com> (raw)
From: Devansh Patel <devanshp@cisco.com>
The default product-only mapping cannot cover NVD records published under
Podman's former libpod name. podman_project:podman is the active NVD
dictionary CPE and configuration identity. libpod_project:libpod is the
historical NVD dictionary CPE and configuration identity for the same source
lineage, including records already referenced by recipe CVE_STATUS entries.
The exact pair retains all 23 records from the default mapping and adds
CVE-2018-10856, CVE-2019-10214, and CVE-2019-18466 from the historical NVD
identity.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
recipes-containers/podman/podman_git.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-containers/podman/podman_git.bb b/recipes-containers/podman/podman_git.bb
index e3bd1621..03e22e5d 100644
--- a/recipes-containers/podman/podman_git.bb
+++ b/recipes-containers/podman/podman_git.bb
@@ -29,6 +29,8 @@ GO_IMPORT = "import"
PV = "6.1.0-dev"
+CVE_PRODUCT = "podman_project:podman libpod_project:libpod"
+
CVE_STATUS[CVE-2019-10152] = "fixed-version: fixed since v1.4.0"
CVE_STATUS[CVE-2020-1726] = "fixed-version: fixed since v1.8.1"
CVE_STATUS[CVE-2022-2989] = "fixed-version: fixed since v4.3.0"
--
2.35.6
next reply other threads:[~2026-08-21 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 5:07 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
2026-09-01 13:33 ` [meta-virtualization][PATCH] podman: correct CVE_PRODUCT mapping Bruce Ashfield
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=20260821050709.49931-1-devanshp@cisco.com \
--to=devanshp@cisco.com \
--cc=meta-virtualization@lists.yoctoproject.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