From: Andra Paraschiv <andraprs@amazon.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Mathias Krause <minipli@grsecurity.net>,
ne-devel-upstream <ne-devel-upstream@amazon.com>,
stable <stable@vger.kernel.org>,
Andra Paraschiv <andraprs@amazon.com>
Subject: [PATCH v1 0/1] Nitro Enclaves kernel driver issue fix
Date: Thu, 29 Apr 2021 19:59:40 +0300 [thread overview]
Message-ID: <20210429165941.27020-1-andraprs@amazon.com> (raw)
An issue was found in the Nitro Enclaves kernel driver codebase [1] included in
the v5.10 upstream Linux kernel. The fix for it has been tested on the AWS side.
The issue does not break the isolation or security of what is running inside the
enclave. Nitro Enclaves already assumes that the instance running the Nitro
Enclaves kernel driver is untrusted.
We would like to thank Mathias Krause from Open Source Security, Inc. for
reporting and providing a fix for this issue directly to AWS.
The patch will be merged into the latest upstream Linux kernel release and into
the v5.10+ stable kernel releases.
Thanks,
Andra
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/virt/nitro_enclaves
Mathias Krause (1):
nitro_enclaves: Fix stale file descriptors on failed usercopy
drivers/virt/nitro_enclaves/ne_misc_dev.c | 43 +++++++++--------------
1 file changed, 17 insertions(+), 26 deletions(-)
--
2.20.1 (Apple Git-117)
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
next reply other threads:[~2021-04-29 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 16:59 Andra Paraschiv [this message]
2021-04-29 16:59 ` [PATCH v1 1/1] nitro_enclaves: Fix stale file descriptors on failed usercopy Andra Paraschiv
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=20210429165941.27020-1-andraprs@amazon.com \
--to=andraprs@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@grsecurity.net \
--cc=ne-devel-upstream@amazon.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).