mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srini@kernel.org>
To: linux-arm-msm@vger.kernel.org,
	 Anandu Krishnan E <anandu.e@oss.qualcomm.com>
Cc: gregkh@linuxfoundation.org, quic_bkumar@quicinc.com,
	 linux-kernel@vger.kernel.org, quic_chennak@quicinc.com,
	 dri-devel@lists.freedesktop.org, arnd@arndb.de,
	 ekansh.gupta@oss.qualcomm.com, stable@kernel.org
Subject: Re: [PATCH v4] misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context
Date: Tue, 19 May 2026 17:01:59 +0100	[thread overview]
Message-ID: <177920651904.51472.16101417820040799306.b4-ty@kernel.org> (raw)
In-Reply-To: <20260518203507.3754994-1-anandu.e@oss.qualcomm.com>


On Tue, 19 May 2026 02:05:07 +0530, Anandu Krishnan E wrote:
> There is a race between fastrpc_device_release() and the workqueue
> that processes DSP responses. When the user closes the file descriptor,
> fastrpc_device_release() frees the fastrpc_user structure. Concurrently,
> an in-flight DSP invocation can complete and fastrpc_rpmsg_callback()
> schedules context cleanup via schedule_work(&ctx->put_work). If the
> workqueue runs fastrpc_context_free() in parallel with or after
> fastrpc_device_release() has freed the user structure, it dereferences
> the freed fastrpc_user. Depending on the state of the context at the
> time of the race, any one of the following accesses can be hit:
> 
> [...]

Applied, thanks!

[1/1] misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context
      commit: b01bf21ae7e7c4c7cd4f1c8419bafc1e04c008e4

Best regards,
-- 
Srinivas Kandagatla <srini@kernel.org>


      reply	other threads:[~2026-05-19 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 20:35 Anandu Krishnan E
2026-05-19 16:01 ` Srinivas Kandagatla [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=177920651904.51472.16101417820040799306.b4-ty@kernel.org \
    --to=srini@kernel.org \
    --cc=anandu.e@oss.qualcomm.com \
    --cc=arnd@arndb.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_bkumar@quicinc.com \
    --cc=quic_chennak@quicinc.com \
    --cc=stable@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®