From: Greg KH <gregkh@linuxfoundation.org>
To: Xiangyu Chen <xiangyu.chen@windriver.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.1] Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails
Date: Wed, 9 Oct 2024 15:33:47 +0200 [thread overview]
Message-ID: <2024100900-lavish-implosive-4107@gregkh> (raw)
In-Reply-To: <20241009081627.354405-1-xiangyu.chen@windriver.com>
On Wed, Oct 09, 2024 at 04:16:26PM +0800, Xiangyu Chen wrote:
> From: Rick Edgecombe <rick.p.edgecombe@intel.com>
>
> In CoCo VMs it is possible for the untrusted host to cause
> set_memory_encrypted() or set_memory_decrypted() to fail such that an
> error is returned and the resulting memory is shared. Callers need to
> take care to handle these errors to avoid returning decrypted (shared)
> memory to the page allocator, which could lead to functional or security
> issues.
>
> VMBus code could free decrypted pages if set_memory_encrypted()/decrypted()
> fails. Leak the pages if this happens.
>
> Signed-off-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
> Signed-off-by: Michael Kelley <mhklinux@outlook.com>
> Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Link: https://lore.kernel.org/r/20240311161558.1310-2-mhklinux@outlook.com
> Signed-off-by: Wei Liu <wei.liu@kernel.org>
> Message-ID: <20240311161558.1310-2-mhklinux@outlook.com>
> [Xiangyu: Modified to apply on 6.1.y]
> Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
> ---
> drivers/hv/connection.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
Are you sure? This is _VERY_ different from what you suggested for
5.15.y and what is in mainline. Also, you didn't show the git id for
the upstream commit.
Please work to figure this out and resend working versions for ALL
affected branches as new patches.
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-09 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 8:16 [PATCH 6.1] Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails Xiangyu Chen
2024-10-09 8:16 ` [PATCH v2 6.1/6.6] wifi: mac80211: Avoid address calculations via out of bounds array indexing Xiangyu Chen
2024-10-09 13:34 ` Greg KH
2024-10-09 13:33 ` Greg KH [this message]
2024-10-10 2:53 ` [PATCH 6.1] Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails Xiangyu Chen
-- strict thread matches above, loose matches on Subject: below --
2024-10-31 2:10 Xiangyu Chen
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=2024100900-lavish-implosive-4107@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=xiangyu.chen@windriver.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