public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Cc: Peter Marko <peter.marko@siemens.com>
Subject: [PATCH 4/6] screen: set status for CVE-2025-46802
Date: Mon, 13 Apr 2026 23:14:45 +0200	[thread overview]
Message-ID: <20260413211447.564257-4-peter.marko@siemens.com> (raw)
In-Reply-To: <20260413211447.564257-1-peter.marko@siemens.com>

From: Peter Marko <peter.marko@siemens.com>

This CVE is showing in the new sbom CVE reports.
It is fixed via [1] which is included in:

$git tag --contains d10eb5b2f7eebaa347f09c010bd391373fdd1695
v.5.0.1

[1] https://cgit.git.savannah.gnu.org/cgit/screen.git/commit/?id=d10eb5b2f7eebaa347f09c010bd391373fdd1695

Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
 meta/recipes-extended/screen/screen_5.0.1.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-extended/screen/screen_5.0.1.bb b/meta/recipes-extended/screen/screen_5.0.1.bb
index 69f4098519..0155ece374 100644
--- a/meta/recipes-extended/screen/screen_5.0.1.bb
+++ b/meta/recipes-extended/screen/screen_5.0.1.bb
@@ -44,3 +44,5 @@ pkg_postinst:${PN} () {
 pkg_postrm:${PN} () {
 	printf "$(grep -v "^${bindir}/screen$" $D${sysconfdir}/shells)\n" > $D${sysconfdir}/shells
 }
+
+CVE_STATUS[CVE-2025-46802] = "fixed-version: fixed since 5.0.1"


  parent reply	other threads:[~2026-04-13 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 21:14 [PATCH 1/6] xdg-utils: set status for CVE-2025-52968 Peter Marko
2026-04-13 21:14 ` [PATCH 2/6] wic: set CVE_PRODUCT Peter Marko
2026-04-13 21:14 ` [PATCH 3/6] tar: set status for CVE-2025-45582 Peter Marko
2026-04-13 21:14 ` Peter Marko [this message]
2026-04-13 21:14 ` [PATCH 5/6] ovmf: set status for CVE-2024-1298 Peter Marko
2026-04-13 21:14 ` [PATCH 6/6] mpg123: set status for CVE-2006-3355 Peter Marko
2026-04-13 21:23   ` Marko, Peter
2026-04-14  6:44     ` 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=20260413211447.564257-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