public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jijie Shao <shaojijie@huawei.com>
To: Duoming Zhou <duoming@zju.edu.cn>, <netdev@vger.kernel.org>
Cc: <shaojijie@huawei.com>, <linux-atm-general@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>, <3chas3@gmail.com>
Subject: Re: [PATCH net v2] atm: fore200e: fix use-after-free in tasklets during device removal
Date: Fri, 6 Feb 2026 18:48:38 +0800	[thread overview]
Message-ID: <41559748-63f2-49ea-9d94-433eeb0edb8b@huawei.com> (raw)
In-Reply-To: <20260206094811.23431-1-duoming@zju.edu.cn>


on 2026/2/6 17:48, Duoming Zhou wrote:
> When the PCA-200E or SBA-200E adapter is being detached, the fore200e
> is deallocated. However, the tx_tasklet or rx_tasklet may still be running
> or pending, leading to use-after-free bug when the already freed fore200e
> is accessed again in fore200e_tx_tasklet() or fore200e_rx_tasklet().
>
> One of the race conditions can occur as follows:
>
> CPU 0 (cleanup)           | CPU 1 (tasklet)
> fore200e_pca_remove_one() | fore200e_interrupt()
>    fore200e_shutdown()     |   tasklet_schedule()
>      kfree(fore200e)       | fore200e_tx_tasklet()
>                            |   fore200e-> // UAF
>
> Fix this by ensuring tx_tasklet or rx_tasklet is properly canceled before
> the fore200e is released. Add tasklet_kill() in fore200e_shutdown() to
> synchronize with any pending or running tasklets. Moreover, since
> fore200e_reset() could prevent further interrupts or data transfers,
> the tasklet_kill() should be placed after fore200e_reset() to prevent
> the tasklet from being rescheduled in fore200e_interrupt().
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> ---
> Changes in v2:
>    - Move tasklet_kill() after fore200e_reset().
>
>   drivers/atm/fore200e.c | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/drivers/atm/fore200e.c b/drivers/atm/fore200e.c
> index f62e3857144..de04c407921 100644
> --- a/drivers/atm/fore200e.c
> +++ b/drivers/atm/fore200e.c
> @@ -362,6 +362,10 @@ fore200e_shutdown(struct fore200e* fore200e)
>       if (fore200e->state > FORE200E_STATE_RESET) {
>   	/* first, reset the board to prevent further interrupts or data transfers */
>   	fore200e_reset(fore200e, 0);
> +#ifdef FORE200E_USE_TASKLET
> +	tasklet_kill(&fore200e->tx_tasklet);
> +	tasklet_kill(&fore200e->rx_tasklet);
> +#endif
>       }

I'm sorry if I gave you a confusing comment.

If (fore200e->state <= FORE200E_STATE_RESET), is there no need to do tasklet_kill()?

Tips: If you need to send v3, please don’t repost your patche within one 24h period:
   https://www.kernel.org/doc/html/next/process/maintainer-netdev.html

   Jijie Shao


  reply	other threads:[~2026-02-06 10:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06  9:48 [PATCH net v2] atm: fore200e: fix use-after-free in tasklets during device removal Duoming Zhou
2026-02-06 10:48 ` Jijie Shao [this message]
2026-02-06 14:56   ` duoming
2026-02-09  6:41     ` Jijie Shao
2026-02-09  8:30       ` duoming

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=41559748-63f2-49ea-9d94-433eeb0edb8b@huawei.com \
    --to=shaojijie@huawei.com \
    --cc=3chas3@gmail.com \
    --cc=duoming@zju.edu.cn \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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