netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: andrew+netdev@lunn.ch, brett.creeley@amd.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net] pds_core: remove write-after-free of client_id
Date: Mon, 28 Apr 2025 20:21:19 +0100	[thread overview]
Message-ID: <20250428192119.GI3339421@horms.kernel.org> (raw)
In-Reply-To: <20250425203857.71547-1-shannon.nelson@amd.com>

On Fri, Apr 25, 2025 at 01:38:57PM -0700, Shannon Nelson wrote:
> A use-after-free error popped up in stress testing:
> 
> [Mon Apr 21 21:21:33 2025] BUG: KFENCE: use-after-free write in pdsc_auxbus_dev_del+0xef/0x160 [pds_core]
> [Mon Apr 21 21:21:33 2025] Use-after-free write at 0x000000007013ecd1 (in kfence-#47):
> [Mon Apr 21 21:21:33 2025]  pdsc_auxbus_dev_del+0xef/0x160 [pds_core]
> [Mon Apr 21 21:21:33 2025]  pdsc_remove+0xc0/0x1b0 [pds_core]
> [Mon Apr 21 21:21:33 2025]  pci_device_remove+0x24/0x70
> [Mon Apr 21 21:21:33 2025]  device_release_driver_internal+0x11f/0x180
> [Mon Apr 21 21:21:33 2025]  driver_detach+0x45/0x80
> [Mon Apr 21 21:21:33 2025]  bus_remove_driver+0x83/0xe0
> [Mon Apr 21 21:21:33 2025]  pci_unregister_driver+0x1a/0x80
> 
> The actual device uninit usually happens on a separate thread
> scheduled after this code runs, but there is no guarantee of order
> of thread execution, so this could be a problem.  There's no
> actual need to clear the client_id at this point, so simply
> remove the offending code.
> 
> Fixes: 10659034c622 ("pds_core: add the aux client API")
> Signed-off-by: Shannon Nelson <shannon.nelson@amd.com>

Thinking out loud:

My understanding is that after auxiliary_device_uninit() has
been called then pdsc_auxbus_dev_release(), which frees the memory
used by padev, will be called asynchronously.

And, as per the patch description, this usually happens after
the line deleted by this patch has been executed. But there are no
guarantees about that ordering. And sometimes it does not. *Boom*.

Based on my understanding above this patch looks good to me.

Reviewed-by: Simon Horman <horms@kernel.org>

> ---
>  drivers/net/ethernet/amd/pds_core/auxbus.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/amd/pds_core/auxbus.c b/drivers/net/ethernet/amd/pds_core/auxbus.c
> index c9aac27883a3..92f359f2b449 100644
> --- a/drivers/net/ethernet/amd/pds_core/auxbus.c
> +++ b/drivers/net/ethernet/amd/pds_core/auxbus.c
> @@ -186,7 +186,6 @@ void pdsc_auxbus_dev_del(struct pdsc *cf, struct pdsc *pf,
>  	pds_client_unregister(pf, padev->client_id);
>  	auxiliary_device_delete(&padev->aux_dev);
>  	auxiliary_device_uninit(&padev->aux_dev);
> -	padev->client_id = 0;
>  	*pd_ptr = NULL;
>  
>  	mutex_unlock(&pf->config_lock);
> -- 
> 2.17.1
> 
> 

  reply	other threads:[~2025-04-28 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 20:38 [PATCH net] pds_core: remove write-after-free of client_id Shannon Nelson
2025-04-28 19:21 ` Simon Horman [this message]
2025-04-28 23:00 ` patchwork-bot+netdevbpf

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=20250428192119.GI3339421@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=brett.creeley@amd.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shannon.nelson@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;
as well as URLs for NNTP newsgroup(s).