From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@axis.com>,
Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: [PATCH 1/2] dmaengine: Fix use-after-free on release
Date: Mon, 17 Jul 2023 15:08:40 +0200 [thread overview]
Message-ID: <20230717-dummy-dmac-v1-1-24348b6fb56b@axis.com> (raw)
In-Reply-To: <20230717-dummy-dmac-v1-0-24348b6fb56b@axis.com>
Many dmaengine drivers cannot be safely unbound while being used since
they free their device structures in their platform driver ->remove()
callbacks or with devm. In order to avoid this, the framework allows
drivers to implement ->device_release() and free these structures there
instead. However, there are use-after-frees in the framework even when
->device_release() is implemented.
For example, the following sequence of commands with the upcoming
dummy-dmac driver triggers a KASAN splat without this patch:
# insmod dummy-dmac.ko
# insmod dmatest.ko iterations=1 wait=1 run=1
# echo dummy-dmac > /sys/bus/platform/drivers/dummy-dmac/unbind
# rmmod dmatest
==================================================================
BUG: KASAN: slab-use-after-free in dma_chan_put (drivers/dma/dmaengine.c:517)
Read of size 8 at addr ffff888008b00c78 by task rmmod/1063
Call Trace:
dma_chan_put (drivers/dma/dmaengine.c:517)
dma_release_channel (drivers/dma/dmaengine.c:910)
cleanup_module (drivers/dma/dmatest.c:1184) dmatest
...
Allocated by task 859:
kmalloc_trace (mm/slab_common.c:1082)
dummy_dmac_probe (drivers/dma/dummy-dmac.c:171) dummy_dmac
platform_probe (drivers/base/platform.c:1405)
...
Freed by task 1063:
kfree (mm/slab_common.c:1035)
dummy_dmac_release (drivers/dma/dummy-dmac.c:160) dummy_dmac
dma_device_put (include/linux/kref.h:65 drivers/dma/dmaengine.c:437)
dma_chan_put (drivers/dma/dmaengine.c:517)
dma_release_channel (drivers/dma/dmaengine.c:910)
cleanup_module (drivers/dma/dmatest.c:1184) dmatest
...
==================================================================
Fix this by making the framework not touch the dev and client structures
after the last call to dma_device_put().
Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
---
drivers/dma/dmaengine.c | 30 +++++++++++++++++++++---------
1 file changed, 21 insertions(+), 9 deletions(-)
diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
index 826b98284fa1..86b892df8ea1 100644
--- a/drivers/dma/dmaengine.c
+++ b/drivers/dma/dmaengine.c
@@ -485,13 +485,7 @@ static int dma_chan_get(struct dma_chan *chan)
return ret;
}
-/**
- * dma_chan_put - drop a reference to a DMA channel's parent driver module
- * @chan: channel to release
- *
- * Must be called under dma_list_mutex.
- */
-static void dma_chan_put(struct dma_chan *chan)
+static void __dma_chan_put(struct dma_chan *chan)
{
/* This channel is not in use, bail out */
if (!chan->client_count)
@@ -512,9 +506,22 @@ static void dma_chan_put(struct dma_chan *chan)
chan->router = NULL;
chan->route_data = NULL;
}
+}
+
+/**
+ * dma_chan_put - drop a reference to a DMA channel's parent driver module
+ * @chan: channel to release
+ *
+ * Must be called under dma_list_mutex.
+ */
+static void dma_chan_put(struct dma_chan *chan)
+{
+ struct module *owner = dma_chan_to_owner(chan);
+
+ __dma_chan_put(chan);
dma_device_put(chan->device);
- module_put(dma_chan_to_owner(chan));
+ module_put(owner);
}
enum dma_status dma_sync_wait(struct dma_chan *chan, dma_cookie_t cookie)
@@ -902,10 +909,12 @@ EXPORT_SYMBOL_GPL(dma_request_chan_by_mask);
void dma_release_channel(struct dma_chan *chan)
{
+ struct module *owner = dma_chan_to_owner(chan);
+
mutex_lock(&dma_list_mutex);
WARN_ONCE(chan->client_count != 1,
"chan reference count %d != 1\n", chan->client_count);
- dma_chan_put(chan);
+ __dma_chan_put(chan);
/* drop PRIVATE cap enabled by __dma_request_channel() */
if (--chan->device->privatecnt == 0)
dma_cap_clear(DMA_PRIVATE, chan->device->cap_mask);
@@ -922,6 +931,9 @@ void dma_release_channel(struct dma_chan *chan)
kfree(chan->dbg_client_name);
chan->dbg_client_name = NULL;
#endif
+
+ dma_device_put(chan->device);
+ module_put(owner);
mutex_unlock(&dma_list_mutex);
}
EXPORT_SYMBOL_GPL(dma_release_channel);
--
2.34.1
next prev parent reply other threads:[~2023-07-17 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 13:08 [PATCH 0/2] dmaengine: Use-after-free fix and dummy DMAC Vincent Whitchurch
2023-07-17 13:08 ` Vincent Whitchurch [this message]
2023-07-17 13:08 ` [PATCH 2/2] dmaengine: Add dummy DMA controller driver Vincent Whitchurch
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=20230717-dummy-dmac-v1-1-24348b6fb56b@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=dmaengine@vger.kernel.org \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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®