mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Cong Nguyen <congnt264@gmail.com>
Cc: Simon Guinot <sguinot@lacie.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (gpio-fan) fix use-after-free of alarm_work on unbind
Date: Mon, 14 Sep 2026 08:40:34 -0700	[thread overview]
Message-ID: <44026532-e454-458a-847a-9e66e7ddc3ad@roeck-us.net> (raw)
In-Reply-To: <20260914115448.2039438-1-congnt264@gmail.com>

On 9/14/26 04:54, Cong Nguyen wrote:
> fan_alarm_irq_handler() schedules alarm_work, but nothing ever cancels
> it. free_irq() (via devm) only waits for an in-progress IRQ handler,
> not queued work -- a pending alarm_work can run after fan_data is
> devm-freed, dereferencing it in fan_alarm_notify().
> 
> Cancel it via a devm action registered before devm_request_irq(), so
> teardown frees the IRQ first, then cancels whatever's already queued.
> 
> Fixes: d6fe1360f42e ("hwmon: add generic GPIO fan driver")
> Reported-by: Sashiko AI review <sashiko-bot@kernel.org>
> Link: https://lore.kernel.org/r/20260830152150.27F5F1F000E9@smtp.kernel.org
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-4
> Signed-off-by: Cong Nguyen <congnt264@gmail.com>
> ---
>   drivers/hwmon/gpio-fan.c | 20 +++++++++++++++++++-
>   1 file changed, 19 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/hwmon/gpio-fan.c b/drivers/hwmon/gpio-fan.c
> index 084828e1e281..b1b57bb63a33 100644
> --- a/drivers/hwmon/gpio-fan.c
> +++ b/drivers/hwmon/gpio-fan.c
> @@ -81,9 +81,16 @@ static ssize_t fan1_alarm_show(struct device *dev,
>   
>   static DEVICE_ATTR_RO(fan1_alarm);
>   
> +static void gpio_fan_cancel_alarm_work(void *data)
> +{
> +	struct gpio_fan_data *fan_data = data;
> +
> +	cancel_work_sync(&fan_data->alarm_work);

I think this still leaves a window on teardown, if an interrupt happens after
the work was canceled. I would suggest to use disable_work_sync() instead.

Thanks,
Guenter
> +}
> +
>   static int fan_alarm_init(struct gpio_fan_data *fan_data)
>   {
> -	int alarm_irq;
> +	int alarm_irq, err;
>   	struct device *dev = fan_data->dev;
>   
>   	/*
> @@ -95,6 +102,17 @@ static int fan_alarm_init(struct gpio_fan_data *fan_data)
>   		return 0;
>   
>   	INIT_WORK(&fan_data->alarm_work, fan_alarm_notify);
> +
> +	/*
> +	 * Register before devm_request_irq() below: LIFO teardown must free
> +	 * the IRQ (stopping new schedule_work() calls) before this cancels
> +	 * whatever alarm_work is already queued or running.
> +	 */
> +	err = devm_add_action_or_reset(dev, gpio_fan_cancel_alarm_work,
> +					fan_data);
> +	if (err)
> +		return err;
> +
>   	irq_set_irq_type(alarm_irq, IRQ_TYPE_EDGE_BOTH);
>   	return devm_request_irq(dev, alarm_irq, fan_alarm_irq_handler,
>   				IRQF_SHARED, "GPIO fan alarm", fan_data);


  reply	other threads:[~2026-09-14 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 11:54 Cong Nguyen
2026-09-14 15:40 ` Guenter Roeck [this message]
2026-09-15  3:55   ` Nguyễn Công

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=44026532-e454-458a-847a-9e66e7ddc3ad@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=congnt264@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sguinot@lacie.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

all inboxes | Powered by JetHome®