From: Sumit Garg <sumit.garg@kernel.org>
To: Georgiy Osokin <g.osokin@auroraos.dev>
Cc: Jens Wiklander <jenswi@kernel.org>,
op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()
Date: Thu, 1 Oct 2026 18:31:32 +0530 [thread overview]
Message-ID: <ar5ZrHihBjaFKf5U@sumit-xelite> (raw)
In-Reply-To: <20260928143113.1700001-1-g.osokin@auroraos.dev>
On Mon, 28 Sep 2026 at 17:31:13 +0300, Georgiy Osokin wrote:
>tee_dyn_shm_alloc_helper() derives nr_pages from a caller-supplied size
>and passes it to alloc_pages_exact() without checking it. For size == 0
>nr_pages is 0, and alloc_pages_exact(0) calls get_order(0), which is
>documented as undefined and returns BITS_PER_LONG - PAGE_SHIFT. The page
>allocator then trips its order > MAX_PAGE_ORDER warning and fails the
>allocation; on a panic_on_warn kernel that ends the boot.
>
>This can be triggered by TEE_IOC_SHM_ALLOC with struct
>tee_ioctl_shm_alloc_data where size is 0.
>
>Reject a zero page count, as register_shm_helper() already does for the
>register path.
>
>Fixes: cf4441503e20 ("tee: optee: Move pool_op helper functions")
>Cc: stable@vger.kernel.org
>Cc: lvc-project@linuxtesting.org
>Signed-off-by: Georgiy Osokin <g.osokin@auroraos.dev>
>---
> drivers/tee/tee_shm.c | 4 ++++
> 1 file changed, 4 insertions(+)
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
-Sumit
>
>diff --git a/drivers/tee/tee_shm.c b/drivers/tee/tee_shm.c
>index 6742b3579..daa4af1e0 100644
>--- a/drivers/tee/tee_shm.c
>+++ b/drivers/tee/tee_shm.c
>@@ -343,6 +343,10 @@ int tee_dyn_shm_alloc_helper(struct tee_shm *shm, size_t size, size_t align,
> unsigned int i;
> int rc = 0;
>
>+ /* get_order(0) is undefined and exceeds MAX_PAGE_ORDER. */
>+ if (!nr_pages)
>+ return -EINVAL;
>+
> /*
> * Ignore alignment since this is already going to be page aligned
> * and there's no need for any larger alignment.
>
>base-commit: 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e
>--
>2.54.0
>
prev parent reply other threads:[~2026-10-01 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 14:31 Georgiy Osokin
2026-10-01 13:01 ` Sumit Garg [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=ar5ZrHihBjaFKf5U@sumit-xelite \
--to=sumit.garg@kernel.org \
--cc=g.osokin@auroraos.dev \
--cc=jenswi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=op-tee@lists.trustedfirmware.org \
--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
all inboxes | Powered by JetHome®