[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240619084750.9207-1-lirongqing@baidu.com>
Date: Wed, 19 Jun 2024 16:47:50 +0800
From: Li RongQing <lirongqing@...du.com>
To: kirill.shutemov@...ux.intel.com,
dave.hansen@...ux.intel.com,
x86@...nel.org,
linux-coco@...ts.linux.dev,
linux-kernel@...r.kernel.org,
rick.p.edgecombe@...el.com
Cc: Li RongQing <lirongqing@...du.com>
Subject: [PATCH][v3] virt: tdx-guest: Don't free decrypted memory
In CoCo VMs it is possible for the untrusted host to cause
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. So leak the decrypted memory when
set_memory_decrypted fails, and don't need to print an error
since set_memory_decrypted will call WARN_ONCE.
Reviewed-by: Rick Edgecombe <rick.p.edgecombe@...el.com>
Signed-off-by: Li RongQing <lirongqing@...du.com>
---
diff with v2: remove print error
diff with v1: leak the page, and print error
drivers/virt/coco/tdx-guest/tdx-guest.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/virt/coco/tdx-guest/tdx-guest.c b/drivers/virt/coco/tdx-guest/tdx-guest.c
index 1253bf7..8575d98 100644
--- a/drivers/virt/coco/tdx-guest/tdx-guest.c
+++ b/drivers/virt/coco/tdx-guest/tdx-guest.c
@@ -124,10 +124,8 @@ static void *alloc_quote_buf(void)
if (!addr)
return NULL;
- if (set_memory_decrypted((unsigned long)addr, count)) {
- free_pages_exact(addr, len);
+ if (set_memory_decrypted((unsigned long)addr, count))
return NULL;
- }
return addr;
}
--
2.9.4
Powered by blists - more mailing lists