From: Aubin Constans <aubin.constans@microchip.com>
To: Pei Xiao <xiaopei01@kylinos.cn>, <ulfh@kernel.org>,
<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<claudiu.beznea@tuxon.dev>, <linux-mmc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition
Date: Fri, 7 Aug 2026 19:23:39 +0200 [thread overview]
Message-ID: <e4960897-fe77-41c2-95c6-56038b7c9ba2@microchip.com> (raw)
In-Reply-To: <4389d5deff90b2b860bd07f17668270fda36bd26.1785750407.git.xiaopei01@kylinos.cn>
On 03/08/2026 11:48, Pei Xiao wrote:
> In atmci_probe, &host->bh_work is bound with atmci_work_func, and> atmci_interrupt, atmci_timeout_timer and atmci_dma_complete can all
> queue this work on system_bh_wq.
>
> If we remove the module, atmci_remove makes cleanup and the memory
> allocated for host with devm_kzalloc() is released after the remove
> callback returns, while the work mentioned above may still be pending
> or running. The sequence of operations that may lead to a UAF bug is
> as follows:
Thank you for having spotted the issue, and sent this fix.
>
> CPU0 CPU1
>
> | atmci_interrupt
> | queue_work(system_bh_wq,
> | &host->bh_work)
> atmci_remove |
> atmci_cleanup_slot(...) |
> atmci_writel(host, ATMCI_IDR, ~0UL) |
> timer_delete_sync(&host->timer) |
> dma_release_channel(host->dma.chan) |
> free_irq(platform_get_irq(pdev, 0), host) |
> | atmci_work_func
> | // use host
> // devm resources released after |
> // remove returns, host is freed |
> | // use host (use-after-free)
>
> Fix it by canceling the work after all the sources that can schedule
> it (IRQ handler, timeout timer and DMA completion callback) have been
> stopped, and before proceeding with the remaining cleanup in
> atmci_remove.
For completeness, PDC completion could be added to the above list of sources,
even though it is a subroutine of the IRQ handler.
PDC and DMA are exclusive.
Mentioning on which board or MPU the patch was tested would also be a welcome
addition.
>
> Fixes: 7d2be0749a59 ("atmel-mci: Driver for Atmel on-chip MMC controllers")
> Assisted-by: Codex:deepseek-v4-flash
> Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
> ---
> drivers/mmc/host/atmel-mci.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mmc/host/atmel-mci.c b/drivers/mmc/host/atmel-mci.c
> index 3b4928f5b9b2..8f4df250a77a 100644
> --- a/drivers/mmc/host/atmel-mci.c
> +++ b/drivers/mmc/host/atmel-mci.c
> @@ -2610,6 +2610,8 @@ static void atmci_remove(struct platform_device *pdev)
>
> free_irq(platform_get_irq(pdev, 0), host);
>
> + cancel_work_sync(&host->bh_work);
> +
> clk_disable_unprepare(host->mck);
>
> pm_runtime_disable(dev);
> --
> 2.25.1
>
prev parent reply other threads:[~2026-08-07 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 9:48 [PATCH] mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition Pei Xiao
2026-08-04 13:43 ` Ulf Hansson
2026-08-07 17:23 ` Aubin Constans [this message]
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=e4960897-fe77-41c2-95c6-56038b7c9ba2@microchip.com \
--to=aubin.constans@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=ulfh@kernel.org \
--cc=xiaopei01@kylinos.cn \
/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