From: Javier Tia <javier@peridio.com>
To: meta-arm@lists.yoctoproject.org
Cc: Jon Mason <jon.mason@arm.com>, Javier Tia <javier@peridio.com>
Subject: [wrynose PATCH 1/4] arm/optee: modify CVE_PRODUCT
Date: Wed, 2 Sep 2026 16:26:43 -0600 [thread overview]
Message-ID: <20260902222646.2945592-2-javier@peridio.com> (raw)
In-Reply-To: <20260902222646.2945592-1-javier@peridio.com>
From: Jon Mason <jon.mason@arm.com>
Per https://nvd.nist.gov/products/cpe/detail/EB42962B-24FD-4716-B3E2-69F3258A57CF
adding "trustedfirmware:op-tee"
We can probably remove "linaro:op-tee", since it has been depreciated.
Fearing unintended issues, leaving it in for now.
Signed-off-by: Jon Mason <jon.mason@arm.com>
(cherry picked from commit 81f5a92193d37027670f2c9b767ccbcd29d1e78c)
Signed-off-by: Javier Tia <javier@peridio.com>
---
meta-arm/recipes-security/optee/optee-os.inc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta-arm/recipes-security/optee/optee-os.inc b/meta-arm/recipes-security/optee/optee-os.inc
index 076e482b..95c41fb1 100644
--- a/meta-arm/recipes-security/optee/optee-os.inc
+++ b/meta-arm/recipes-security/optee/optee-os.inc
@@ -8,7 +8,9 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=c1f21c4f72f372ef38a5a4aee55ec173"
inherit deploy python3native
require optee.inc
-CVE_PRODUCT = "linaro:op-tee op-tee:op-tee_os"
+CVE_PRODUCT = "linaro:op-tee \
+ op-tee:op-tee_os \
+ trustedfirmware:op-tee"
DEPENDS = "python3-pyelftools-native python3-cryptography-native"
--
Javier Tia
next prev parent reply other threads:[~2026-09-02 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 22:26 [wrynose PATCH 0/4] backport the CVE_PRODUCT fixes from master Javier Tia
2026-09-02 22:26 ` Javier Tia [this message]
2026-09-02 22:26 ` [wrynose PATCH 2/4] arm/trusted-firmware-a: modify CVE_PRODUCT Javier Tia
2026-09-02 22:26 ` [wrynose PATCH 3/4] arm/trusted-firmware-m: add CVE_PRODUCT Javier Tia
2026-09-02 22:26 ` [wrynose PATCH 4/4] arm/scp-firmware: " Javier Tia
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=20260902222646.2945592-2-javier@peridio.com \
--to=javier@peridio.com \
--cc=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.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 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.