From: Simon Horman <horms@kernel.org>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-atm-general@lists.sourceforge.net, 3chas3@gmail.com,
shaojijie@huawei.com, stable@kernel.org
Subject: Re: [PATCH net v4] atm: fore200e: fix use-after-free in tasklets during device removal
Date: Thu, 12 Feb 2026 17:32:15 +0000 [thread overview]
Message-ID: <aY4On7k7vSlq6Tp5@horms.kernel.org> (raw)
In-Reply-To: <20260210094537.9767-1-duoming@zju.edu.cn>
On Tue, Feb 10, 2026 at 05:45:37PM +0800, 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(). 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. In a word, the tasklet_kill() should be placed in
> the FORE200E_STATE_IRQ branch within the switch...case structure.
>
> 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>
> Reviewed-by: Jijie Shao <shaojijie@huawei.com>
> ---
> Changes in v4:
> - Do tasklet_kill() in "switch(fore200e->state)-case FORE200E_STATE_IRQ" branch.
> - Make the commit messages clearer.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-02-12 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 9:45 [PATCH net v4] atm: fore200e: fix use-after-free in tasklets during device removal Duoming Zhou
2026-02-12 17:32 ` Simon Horman [this message]
2026-02-13 3: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=aY4On7k7vSlq6Tp5@horms.kernel.org \
--to=horms@kernel.org \
--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 \
--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