From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Muhammad Bilal <meatuni001@gmail.com>, herbert@gondor.apana.org.au
Cc: thomas.lendacky@amd.com, john.allen@amd.com, davem@davemloft.net,
bp@alien8.de, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: ccp - fix SFS ioctl race against device teardown
Date: Mon, 21 Sep 2026 20:47:20 -0500 [thread overview]
Message-ID: <ce67be1d-797e-47d0-8d6d-434143a95ca3@amd.com> (raw)
In-Reply-To: <20260919192432.272680-1-meatuni001@gmail.com>
On 9/19/2026 2:24 PM, Muhammad Bilal wrote:
> [You don't often get email from meatuni001@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> sfs_ioctl() reads psp_master->sfs_data and caches it in sfs_dev before
> taking sfs_ioctl_mutex, while sfs_dev_destroy() frees sfs_dev->page
> and sfs_dev->command_buf with no locking at all and only clears
> psp->sfs_data afterwards. A call to sfs_ioctl() that reads sfs_data
> just before sfs_dev_destroy() runs will still acquire the mutex and
> go on to use the now-freed command buffer in send_sfs_cmd().
>
> Have both functions take sfs_ioctl_mutex before touching
> psp->sfs_data, so a call that is already using sfs_dev completes
> before teardown can free it, and a call arriving after teardown sees
> sfs_data cleared and returns -ENODEV instead of racing it.
>
> Fixes: 648dbccc03a0 ("crypto: ccp - Add AMD Seamless Firmware Servicing (SFS) driver")
> Signed-off-by: Muhammad Bilal <meatuni001@gmail.com>
> ---
> drivers/crypto/ccp/sfs.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/crypto/ccp/sfs.c b/drivers/crypto/ccp/sfs.c
> index a4777839790b..530141f8bc74 100644
> --- a/drivers/crypto/ccp/sfs.c
> +++ b/drivers/crypto/ccp/sfs.c
> @@ -111,13 +111,13 @@ static long sfs_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> struct sfs_device *sfs_dev;
> int ret = 0;
>
> + guard(mutex)(&sfs_ioctl_mutex);
> +
> if (!psp_master || !psp_master->sfs_data)
> return -ENODEV;
>
> sfs_dev = psp_master->sfs_data;
>
> - guard(mutex)(&sfs_ioctl_mutex);
> -
> switch (cmd) {
> case SFSIOCFWVERS:
> dev_dbg(sfs_dev->dev, "in SFSIOCFWVERS\n");
> @@ -191,8 +191,11 @@ static void sfs_exit(struct kref *ref)
>
> void sfs_dev_destroy(struct psp_device *psp)
> {
> - struct sfs_device *sfs_dev = psp->sfs_data;
> + struct sfs_device *sfs_dev;
> +
> + guard(mutex)(&sfs_ioctl_mutex);
>
> + sfs_dev = psp->sfs_data;
> if (!sfs_dev)
> return;
>
> --
> 2.55.0
>
Reviewed-by: Ashish Kalra <ashish.kalra@amd.com>
next prev parent reply other threads:[~2026-09-22 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 19:24 Muhammad Bilal
2026-09-22 1:47 ` Kalra, Ashish [this message]
2026-09-23 8:26 ` Thomas Huth
2026-09-23 8:57 ` Herbert Xu
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=ce67be1d-797e-47d0-8d6d-434143a95ca3@amd.com \
--to=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meatuni001@gmail.com \
--cc=thomas.lendacky@amd.com \
/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®