All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	op-tee@lists.trustedfirmware.org
Subject: [GIT PULL] OP-TEE fix for v7.1
Date: Thu, 21 May 2026 16:14:10 +0200	[thread overview]
Message-ID: <20260521141410.GA1708231@rayden> (raw)

Hello soc maintainers,

Please pull this patch fixing a use-after-free race in the OP-TEE driver
where a client exiting prematurely could free a request still being
processed by the supplicant.

This is basically a resend of
https://lore.kernel.org/op-tee/20260316071210.GA2470832@rayden/

Thanks,
Jens


The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jenswi/linux-tee.git tags/optee-fix-for-v7.1

for you to fetch changes up to 387a926ee166814611acecb960207fe2f3c4fd3e:

  tee: optee: prevent use-after-free when the client exits before the supplicant (2026-03-02 14:36:50 +0100)

----------------------------------------------------------------
OP-TEE fix for v7.1

Prevent possible use after free in supplicant communication.

----------------------------------------------------------------
Amirreza Zarrabi (1):
      tee: optee: prevent use-after-free when the client exits before the supplicant

 drivers/tee/optee/supp.c | 107 ++++++++++++++++++++++++++++++++---------------
 1 file changed, 74 insertions(+), 33 deletions(-)

             reply	other threads:[~2026-05-21 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 14:14 Jens Wiklander [this message]
2026-05-28 22:10 ` [GIT PULL] OP-TEE fix for v7.1 patchwork-bot+linux-soc
2026-05-28 22:10 ` patchwork-bot+linux-soc

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=20260521141410.GA1708231@rayden \
    --to=jens.wiklander@linaro.org \
    --cc=arm@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.