From: Haotian Zhang <vulab@iscas.ac.cn>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Mosberger-Tang <davidm@egauge.net>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] usb: host: max3421-hcd: stop SPI thread before freeing its DMA buffers
Date: Fri, 9 Oct 2026 12:44:31 +0800 [thread overview]
Message-ID: <20261009044431.3115704-1-vulab@iscas.ac.cn> (raw)
In max3421_probe(), the error path frees the kmalloc'd tx and rx buffers
with kfree() before calling kthread_stop() on max3421_hcd->spi_thread.
The SPI thread entry point max3421_spi_thread() immediately starts using
those buffers through spi_rd8()/spi_wr8(), so when usb_add_hcd() or
request_irq() fails and the thread is still running, it can access the
freed buffers, giving a use-after-free.
Stop the SPI thread first and only free the tx/rx buffers afterwards.
Fixes: 05dfa5c9bc37 ("usb: host: max3421-hcd: fix "spi_rd8" uses dynamic stack allocation warning")
Assisted-by: DeepSeek-V4.1-Flash
Signed-off-by: Haotian Zhang <vulab@iscas.ac.cn>
---
drivers/usb/host/max3421-hcd.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/max3421-hcd.c b/drivers/usb/host/max3421-hcd.c
index 73e76d0e6973..f7cd3e8d8cae 100644
--- a/drivers/usb/host/max3421-hcd.c
+++ b/drivers/usb/host/max3421-hcd.c
@@ -1922,10 +1922,14 @@ max3421_probe(struct spi_device *spi)
}
if (hcd) {
- kfree(max3421_hcd->tx);
- kfree(max3421_hcd->rx);
+ /*
+ * The SPI thread uses the tx/rx buffers, so it must be
+ * stopped before they are freed.
+ */
if (!IS_ERR_OR_NULL(max3421_hcd->spi_thread))
kthread_stop(max3421_hcd->spi_thread);
+ kfree(max3421_hcd->tx);
+ kfree(max3421_hcd->rx);
usb_put_hcd(hcd);
}
return retval;
--
2.25.1
next reply other threads:[~2026-10-09 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 4:44 Haotian Zhang [this message]
2026-10-09 4:51 ` [PATCH] usb: host: max3421-hcd: stop SPI thread before freeing its DMA buffers sashiko-bot
2026-10-09 6:07 ` Krzysztof Kozlowski
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=20261009044431.3115704-1-vulab@iscas.ac.cn \
--to=vulab@iscas.ac.cn \
--cc=davidm@egauge.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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