From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: stable@vger.kernel.org, Pavel Machek <pavel@denx.de>
Subject: Re: [PATCH for 5.10.y] tee: fix memory leak in tee_shm_register()
Date: Tue, 23 Aug 2022 10:30:22 +0200 [thread overview]
Message-ID: <YwSQHoHoH/kOriOA@kroah.com> (raw)
In-Reply-To: <20220823082326.9155-1-jens.wiklander@linaro.org>
On Tue, Aug 23, 2022 at 10:23:26AM +0200, Jens Wiklander wrote:
> Moves the access_ok() check for valid memory range from user space from
> the function tee_shm_register() to tee_ioctl_shm_register(). With this
> we error out early before anything is done that must be undone on error.
>
> Fixes: 578c349570d2 ("tee: add overflow check in register_shm_helper()")
> Cc: stable@vger.kernel.org # 5.10
> Reported-by: Pavel Machek <pavel@denx.de>
> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
> ---
> Hi,
>
> This patch targets the 5.10.y release to take care of a recently introduced
> issue there.
Thanks, now queued up.
greg k-h
prev parent reply other threads:[~2022-08-23 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 8:23 [PATCH for 5.10.y] tee: fix memory leak in tee_shm_register() Jens Wiklander
2022-08-23 8:30 ` Greg KH [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=YwSQHoHoH/kOriOA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jens.wiklander@linaro.org \
--cc=pavel@denx.de \
--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