From: Jonathan Cameron <jic23@kernel.org>
To: Salah Triki <salah.triki@gmail.com>
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
Subject: Re: [PATCH] iio: trigger: fix use-after-free in viio_trigger_alloc()
Date: Sat, 31 Jan 2026 12:44:16 +0000 [thread overview]
Message-ID: <20260131124416.19576731@jic23-huawei> (raw)
In-Reply-To: <20260131092333.247931-1-salah.triki@gmail.com>
On Sat, 31 Jan 2026 10:23:33 +0100
Salah Triki <salah.triki@gmail.com> wrote:
Hi Salah,
This is a definitely case of the fix not being anywhere as simple
as it might look at first glance.
> Once `device_initialize()` is called, the reference count of the device
> is set to 1. The memory associated with the device must then be
> managed by the kobject reference counting.
>
> In `viio_trigger_alloc()`, if `irq_alloc_descs()` or `kvasprintf()` fails,
> the code currently calls `kfree()`. Using `kfree()` in this case bypasses
> the device's release callback and can lead to a use-after-free or memory
> corruption.
In some cases yes it can cause problems, but please show me an actual
path to this in the description. It should indeed be tidied up.
>
> Fix this by calling `put_device()` instead of `kfree()`. This ensures that
> the memory is freed properly via `iio_trig_release()` when the reference
> count drops to zero.
This change is not sufficient and causes some cleanup to happen twice
thus introducing some bugs that weren't there before.
So take another look.
>
> Fixes: 2c99f1a09da3d ("iio: trigger: clean up viio_trigger_alloc()")
>
No blank line here. Scripts that commonly run on the kernel tree rely
on the the tags block having no blank lines in it to avoid false positives.
> Signed-off-by: Salah Triki <salah.triki@gmail.com>
> ---
> drivers/iio/industrialio-trigger.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/industrialio-trigger.c b/drivers/iio/industrialio-trigger.c
> index 54416a384232..981e19757870 100644
> --- a/drivers/iio/industrialio-trigger.c
> +++ b/drivers/iio/industrialio-trigger.c
> @@ -597,7 +597,7 @@ struct iio_trigger *viio_trigger_alloc(struct device *parent,
> free_descs:
> irq_free_descs(trig->subirq_base, CONFIG_IIO_CONSUMERS_PER_TRIGGER);
> free_trig:
> - kfree(trig);
> + put_device(&trig->dev);
> return NULL;
> }
>
next prev parent reply other threads:[~2026-01-31 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 9:23 [PATCH] iio: trigger: fix use-after-free in viio_trigger_alloc() Salah Triki
2026-01-31 12:44 ` Jonathan Cameron [this message]
2026-02-02 10:12 ` Nuno Sá
2026-02-02 20:52 ` Jonathan Cameron
2026-02-03 11:18 ` Andy Shevchenko
2026-02-03 11:20 ` Andy Shevchenko
2026-02-03 11:26 ` Andy Shevchenko
2026-02-04 20:03 ` Salah Triki
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=20260131124416.19576731@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=salah.triki@gmail.com \
/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