From: Yu Zhang <yuz08559@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, "Yu Zhang" <yuz08559@gmail.com>
Subject: [PATCH] iio: trigger: fix use-after-free in current_trigger_store() on concurrent writers
Date: Mon, 26 Oct 2026 20:02:46 +1000 [thread overview]
Message-ID: <20261026100246.68005-1-yuz08559@gmail.com> (raw)
current_trigger_store() holds iio_dev_opaque->mlock only around the
INDIO_BUFFER_TRIGGERED / trig_readonly checks and then drops it. The rest
runs unlocked: it reads the current trigger into oldtrig, acquires the new
one by name, stores it into indio_dev->trig, and drops the old trigger's
reference with iio_trigger_put().
sysfs does not serialize writes to the same attribute issued through
different open file descriptors (each open has its own kernfs_open_file),
so two threads can run current_trigger_store() on the same
.../trigger/current_trigger concurrently. Both read the same oldtrig, both
overwrite indio_dev->trig, and both call iio_trigger_put(oldtrig). The
extra put drops the trigger's refcount to zero while it is still in use,
frees it, and a concurrent writer then dereferences the freed trigger.
With two sets of writers hammering current_trigger between two software
triggers on an iio_dummy device, KASAN reports:
refcount_t: addition on 0; use-after-free.
WARNING: CPU: 3 PID: 3467 at refcount_warn_saturate+0xbb/0xe0
kobject_get+0xf6/0x100
current_trigger_store+0x15c/0x4b0
...
BUG: KASAN: slab-use-after-free in current_trigger_store+0x168/0x4b0
Freed by task 3468:
kobject_put+0x125/0x220
current_trigger_store+0x2cc/0x4b0
Allocated by task 3454:
__iio_trigger_alloc+0xc7/0x100
...
Oops: general protection fault
__module_get+0x27/0xd0
current_trigger_store+0x192/0x4b0
Hold mlock across the whole operation so that reading oldtrig, swapping
indio_dev->trig and dropping the reference are atomic with respect to
other writers (and to buffer enable, which the -EBUSY check guards).
Acquiring the new trigger with iio_trigger_acquire_by_name() under mlock
is safe: it only takes iio_trigger_list_lock, and the buffer path already
calls iio_trigger_{attach,detach}_poll_func() with mlock held.
Cc: stable@vger.kernel.org
Signed-off-by: Yu Zhang <yuz08559@gmail.com>
---
drivers/iio/industrialio-trigger.c | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/iio/industrialio-trigger.c b/drivers/iio/industrialio-trigger.c
index 76926fe..9241cd6 100644
--- a/drivers/iio/industrialio-trigger.c
+++ b/drivers/iio/industrialio-trigger.c
@@ -441,17 +441,18 @@ static ssize_t current_trigger_store(struct device *dev,
{
struct iio_dev *indio_dev = dev_to_iio_dev(dev);
struct iio_dev_opaque *iio_dev_opaque = to_iio_dev_opaque(indio_dev);
- struct iio_trigger *oldtrig = indio_dev->trig;
+ struct iio_trigger *oldtrig;
struct iio_trigger *trig;
int ret;
- scoped_guard(mutex, &iio_dev_opaque->mlock) {
- if (iio_dev_opaque->currentmode == INDIO_BUFFER_TRIGGERED)
- return -EBUSY;
- if (iio_dev_opaque->trig_readonly)
- return -EPERM;
- }
+ guard(mutex)(&iio_dev_opaque->mlock);
+
+ if (iio_dev_opaque->currentmode == INDIO_BUFFER_TRIGGERED)
+ return -EBUSY;
+ if (iio_dev_opaque->trig_readonly)
+ return -EPERM;
+ oldtrig = indio_dev->trig;
trig = iio_trigger_acquire_by_name(buf);
if (oldtrig == trig) {
ret = len;
--
2.43.0
reply other threads:[~2026-10-26 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261026100246.68005-1-yuz08559@gmail.com \
--to=yuz08559@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=stable@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
all inboxes | Powered by JetHome®