From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, ross.burton@arm.com
Cc: nd@arm.com
Subject: Re: [PATCH 1/2] arm/optee: handle CVE-2021-36133 as disputed
Date: Mon, 13 Nov 2023 10:46:13 -0500 [thread overview]
Message-ID: <169989037229.1070071.14520083062566745586.b4-ty@arm.com> (raw)
In-Reply-To: <20231113133100.2200065-1-ross.burton@arm.com>
On Mon, 13 Nov 2023 13:30:59 +0000, ross.burton@arm.com wrote:
> This CVE is specific to NXP i.MX boards which are documented as being
> shipped unsecure, as they're meant for development.
>
>
Applied, thanks!
[1/2] arm/optee: handle CVE-2021-36133 as disputed
commit: 7fb2707adaa3ef25b48bd58e63b32161f9ba0faf
[2/2] arm-bsp/optee-os: backport fix for CVE-2023-41325
commit: 721ed95a23b6e5cbe8a8ed9c0505eb02ff35d85c
Best regards,
--
Jon Mason <jon.mason@arm.com>
prev parent reply other threads:[~2023-11-13 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 13:30 [PATCH 1/2] arm/optee: handle CVE-2021-36133 as disputed ross.burton
2023-11-13 13:31 ` [PATCH 2/2] arm-bsp/optee-os: backport fix for CVE-2023-41325 ross.burton
2023-11-13 15:46 ` Jon Mason [this message]
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=169989037229.1070071.14520083062566745586.b4-ty@arm.com \
--to=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.com \
--cc=ross.burton@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).