From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Cc: Peter Marko <peter.marko@siemens.com>
Subject: [PATCH 4/6] git: set status of 5 CVEs
Date: Sun, 26 Apr 2026 20:50:23 +0200 [thread overview]
Message-ID: <20260426185025.13217-4-peter.marko@siemens.com> (raw)
In-Reply-To: <20260426185025.13217-1-peter.marko@siemens.com>
From: Peter Marko <peter.marko@siemens.com>
It is unclear why entries in cvelistV5 cause these CVEs to appear in CVE
reports.
There is one which should also not be shown per listed CPEs, however it
does not have a patch, so it's not added to the list - CVE-2024-52005.
The others are set to fixed with version based on which .0 release
included patch mentioned in Debian security tracker for respective CVE.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
meta/recipes-devtools/git/git_2.53.0.bb | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/meta/recipes-devtools/git/git_2.53.0.bb b/meta/recipes-devtools/git/git_2.53.0.bb
index 5fe1767e28..5169e93931 100644
--- a/meta/recipes-devtools/git/git_2.53.0.bb
+++ b/meta/recipes-devtools/git/git_2.53.0.bb
@@ -171,3 +171,9 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
EXTRA_OEMAKE += "NO_GETTEXT=1"
SRC_URI[tarball.sha256sum] = "429dc0f5fe5f14109930cdbbb588c5d6ef5b8528910f0d738040744bebdc6275"
+
+CVE_STATUS[CVE-2024-32002] = "fixed version: fixed since v2.46.0"
+CVE_STATUS[CVE-2024-50349] = "fixed version: fixed since v2.49.0"
+CVE_STATUS[CVE-2024-52006] = "fixed version: fixed since v2.49.0"
+CVE_STATUS[CVE-2025-48385] = "fixed version: fixed since v2.51.0"
+CVE_STATUS[CVE-2025-48386] = "fixed version: fixed since v2.51.0"
next prev parent reply other threads:[~2026-04-26 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 18:50 [PATCH 1/6] sudo: set status of CVE-2025-64170 and CVE-2025-64517 Peter Marko
2026-04-26 18:50 ` [PATCH 2/6] cargo: set status of CVE-2023-40030 Peter Marko
2026-04-26 18:50 ` [PATCH 3/6] cargo: set CVE_PRODUCT Peter Marko
2026-04-26 18:50 ` Peter Marko [this message]
2026-04-26 18:50 ` [PATCH 5/6] ovmf: set status for 7 CVEs Peter Marko
2026-04-26 18:50 ` [PATCH 6/6] ffmpeg: set status for 5 CVEs Peter Marko
2026-04-27 7:44 ` Benjamin Robin
2026-04-27 10:07 ` Marko, Peter
2026-04-27 10:10 ` [PATCH v2] ffmpeg: set status for 4 CVEs Peter Marko
2026-04-27 16:40 ` Marko, Peter
2026-04-26 19:17 ` [PATCH 1/6] sudo: set status of CVE-2025-64170 and CVE-2025-64517 Marko, Peter
2026-04-27 7:12 ` Benjamin Robin
2026-04-28 16:51 ` Marko, Peter
2026-04-29 7:24 ` Benjamin Robin
2026-04-29 17:13 ` Marko, Peter
2026-04-30 7:21 ` Benjamin Robin
2026-04-30 7:32 ` Benjamin Robin
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=20260426185025.13217-4-peter.marko@siemens.com \
--to=peter.marko@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
/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