From: Guenter Roeck <linux@roeck-us.net>
To: Purva Yeshi <purvayeshi550@gmail.com>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: asus_atk0110: NULL buf.pointer after free
Date: Thu, 10 Apr 2025 13:04:08 -0700 [thread overview]
Message-ID: <bba9ff87-90de-4eae-99d1-647ee413d480@roeck-us.net> (raw)
In-Reply-To: <20250410183450.15514-1-purvayeshi550@gmail.com>
On Fri, Apr 11, 2025 at 12:04:50AM +0530, Purva Yeshi wrote:
> Fix Smatch-detected issue:
> drivers/hwmon/asus_atk0110.c:987 atk_enumerate_old_hwmon() error:
> double free of 'buf.pointer' (line 966)
> drivers/hwmon/asus_atk0110.c:1008 atk_enumerate_old_hwmon() error:
> double free of 'buf.pointer' (line 987)
>
> Smatch warns about double free of 'buf.pointer'.
> This happens because the same buffer struct is reused multiple times
> without resetting the pointer after free. Set buf.pointer = NULL
> after each ACPI_FREE to prevent possible use-after-free bugs.
>
> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
> ---
> drivers/hwmon/asus_atk0110.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/hwmon/asus_atk0110.c b/drivers/hwmon/asus_atk0110.c
> index c80350e499e9..83ee7f25bb8e 100644
> --- a/drivers/hwmon/asus_atk0110.c
> +++ b/drivers/hwmon/asus_atk0110.c
> @@ -964,6 +964,7 @@ static int atk_enumerate_old_hwmon(struct atk_data *data)
> count++;
> }
> ACPI_FREE(buf.pointer);
> + buf.pointer = NULL;
>
> /* Temperatures */
> buf.length = ACPI_ALLOCATE_BUFFER;
> @@ -985,6 +986,7 @@ static int atk_enumerate_old_hwmon(struct atk_data *data)
> count++;
> }
> ACPI_FREE(buf.pointer);
> + buf.pointer = NULL;
>
> /* Fans */
> buf.length = ACPI_ALLOCATE_BUFFER;
buf.length is set to ACPI_ALLOCATE_BUFFER to trigger buffer
allocation in acpi_evaluate_object_typed(). The old content of
buf.pointer is irrelevant (and not initialized to start with
in the first call). The problem you describe does not exist.
Guenter
> @@ -1006,6 +1008,7 @@ static int atk_enumerate_old_hwmon(struct atk_data *data)
> count++;
> }
> ACPI_FREE(buf.pointer);
> + buf.pointer = NULL;
>
> return count;
> }
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2025-04-10 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 18:34 Purva Yeshi
2025-04-10 20:04 ` Guenter Roeck [this message]
2025-04-11 6:59 ` Purva Yeshi
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=bba9ff87-90de-4eae-99d1-647ee413d480@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=kronos.it@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=purvayeshi550@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
all inboxes | Powered by JetHome®