[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aElSKF88vBsIOJMV@gondor.apana.org.au>
Date: Wed, 11 Jun 2025 17:53:44 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: T Pratham <t-pratham@...com>
Cc: "David S. Miller" <davem@...emloft.net>,
Kamlesh Gurudasani <kamlesh@...com>,
Vignesh Raghavendra <vigneshr@...com>,
Praneeth Bajjuri <praneeth@...com>,
Manorit Chawdhry <m-chawdhry@...com>, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, Vinod Koul <vkoul@...nel.org>,
dmaengine@...r.kernel.org
Subject: Re: [PATCH v5 2/2] crypto: ti: Add driver for DTHE V2 AES Engine
(ECB, CBC)
On Tue, Jun 03, 2025 at 06:07:29PM +0530, T Pratham wrote:
>
> + // Need to do a timeout to ensure finalise gets called if DMA callback fails for any reason
> + ret = wait_for_completion_timeout(&rctx->aes_compl, msecs_to_jiffies(DTHE_DMA_TIMEOUT_MS));
This doesn't look safe. What if the callback is invoked after a
timeout? That would be a UAF.
Does the DMA engine provide any timeout mechanism? If not, then
you could do it with a delayed work struct. Just make sure that
you cancel the work struct in the normal path callback. Vice versa
you need to terminate the DMA job in the timeout work struct.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists