public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/6] graphene: ignore CVE-2024-1984
Date: Tue, 14 Apr 2026 16:56:47 +0100	[thread overview]
Message-ID: <20260414155652.1214302-1-ross.burton@arm.com> (raw)

This CVE is for a WordPress theme called Graphene.  It's likely that the
CPE for this graphene will be gnome:graphene but this hasn't been
formally documented, so exclude this one CVE for now.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index d14a6403ff4..7aa72b4a78f 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -26,3 +26,5 @@ EXTRA_OEMESON = "-Dinstalled_tests=false"
 FILES:${PN} += "${libdir}/graphene-1.0"
 
 BBCLASSEXTEND = "native nativesdk"
+
+CVE_STATUS[CVE-2024-1984] = "cpe-incorrect: issue in a WordPress theme"
-- 
2.43.0



             reply	other threads:[~2026-04-14 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 15:56 Ross Burton [this message]
2026-04-14 15:56 ` [PATCH 2/6] re2c: backport fix for CVE-2026-2903 Ross Burton
2026-04-14 15:56 ` [PATCH 3/6] python3-requests: backport fix for CVE-2026-25645 Ross Burton
2026-04-14 15:56 ` [PATCH 4/6] libexif: backport fixes for CVE-2026-40385/CVE-2026-40386/CVE-2026-32775 Ross Burton
2026-04-15 19:10   ` [OE-core] " Marko, Peter
2026-04-15 21:13     ` Ross Burton
2026-04-14 15:56 ` [PATCH 5/6] perl: link to the system zlib instead of a vendored copy Ross Burton
2026-04-14 15:56 ` [PATCH 6/6] perl: link to the system bzip2 " Ross Burton

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=20260414155652.1214302-1-ross.burton@arm.com \
    --to=ross.burton@arm.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