mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: duoming@zju.edu.cn
To: "Jijie Shao" <shaojijie@huawei.com>
Cc: netdev@vger.kernel.org, 3chas3@gmail.com,
	linux-atm-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH net v3] atm: fore200e: fix use-after-free in tasklets during device removal
Date: Tue, 10 Feb 2026 13:38:13 +0800 (GMT+08:00)	[thread overview]
Message-ID: <60202c25.703d4.19c460eafca.Coremail.duoming@zju.edu.cn> (raw)
In-Reply-To: <cfa65635-8a78-4929-8490-f66b7a38d02e@huawei.com>

On Tue, 10 Feb 2026 09:46:53 +0800 Jijie Shao 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(). Finally,
> > it only needs to do tasklet_kill() when the fore200e state is greater
> > than or equal to FORE200E_STATE_IRQ, since tasklets are uninitialized
> > in earlier states.
> >
> > This bug was identified through static analysis.
> >
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> > Cc: stable@kernel.org
> > Suggested-by: Jijie Shao <shaojijie@huawei.com>
> > Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> > ---
> > Changes in v3:
> >    - Only do tasklet_kill() when state >= FORE200E_STATE_IRQ.
> >    - Make the commit messages clearer.
> >
> >   drivers/atm/fore200e.c | 7 ++++++-
> >   1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/atm/fore200e.c b/drivers/atm/fore200e.c
> > index f62e3857144..eb386ec6b5e 100644
> > --- a/drivers/atm/fore200e.c
> > +++ b/drivers/atm/fore200e.c
> > @@ -363,7 +363,12 @@ fore200e_shutdown(struct fore200e* fore200e)
> >   	/* first, reset the board to prevent further interrupts or data transfers */
> >   	fore200e_reset(fore200e, 0);
> >       }
> > -
> > +#ifdef FORE200E_USE_TASKLET
> > +	if (fore200e->state >= FORE200E_STATE_IRQ) {
> > +		tasklet_kill(&fore200e->tx_tasklet);
> > +		tasklet_kill(&fore200e->rx_tasklet);
> > +	}
> > +#endif
> 
> The code appears to be misaligned.
> I see that in the original driver code, the first level of indentation uses 4 spaces,
> and the second level uses a TAB (8-character width).
> In your code, the first level uses a TAB, and the second level uses two TABs.
> Of course, your code complies with the current coding standards.
> 
> Additionally, I think a better modification would be to do tasklet_kill()
> in the "switch(fore200e->state)-case FORE200E_STATE_IRQ" branch,
> because "fore200e->tx_tasklet" is initialized together with "fore200e->irq".

Thank you for your suggestions! I will adjust the tasklet_kill() into the
"case FORE200E_STATE_IRQ" branch. The details are as follows:

diff --git a/drivers/atm/fore200e.c b/drivers/atm/fore200e.c
index f62e3857144..fec081db36d 100644
--- a/drivers/atm/fore200e.c
+++ b/drivers/atm/fore200e.c
@@ -373,6 +373,10 @@ fore200e_shutdown(struct fore200e* fore200e)
        fallthrough;
     case FORE200E_STATE_IRQ:
        free_irq(fore200e->irq, fore200e->atm_dev);
+#ifdef FORE200E_USE_TASKLET
+       tasklet_kill(&fore200e->tx_tasklet);
+       tasklet_kill(&fore200e->rx_tasklet);
+#endif

Best regards,
Duoming Zhou

  reply	other threads:[~2026-02-10  5:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09  9:45 Duoming Zhou
2026-02-10  1:46 ` Jijie Shao
2026-02-10  5:38   ` duoming [this message]
2026-02-10  3:37 ` kernel test robot

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=60202c25.703d4.19c460eafca.Coremail.duoming@zju.edu.cn \
    --to=duoming@zju.edu.cn \
    --cc=3chas3@gmail.com \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shaojijie@huawei.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®