From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Hans de Goede <hansg@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer
Date: Mon, 15 Sep 2025 15:24:11 +0300 [thread overview]
Message-ID: <aMgFa9LLJBhjcgJr@kuha.fi.intel.com> (raw)
In-Reply-To: <20250913113515.21698-1-hansg@kernel.org>
On Sat, Sep 13, 2025 at 01:35:15PM +0200, Hans de Goede wrote:
> Since commit 7d5e9737efda ("net: rfkill: gpio: get the name and type from
> device property") rfkill_find_type() gets called with the possibly
> uninitialized "const char *type_name;" local variable.
>
> On x86 systems when rfkill-gpio binds to a "BCM4752" or "LNV4752"
> acpi_device, the rfkill->type is set based on the ACPI acpi_device_id:
>
> rfkill->type = (unsigned)id->driver_data;
>
> and there is no "type" property so device_property_read_string() will fail
> and leave type_name uninitialized, leading to a potential crash.
>
> rfkill_find_type() does accept a NULL pointer, fix the potential crash
> by initializing type_name to NULL.
>
> Note likely sofar this has not been caught because:
>
> 1. Not many x86 machines actually have a "BCM4752"/"LNV4752" acpi_device
> 2. The stack happened to contain NULL where type_name is stored
>
> Fixes: 7d5e9737efda ("net: rfkill: gpio: get the name and type from device property")
> Cc: stable@vger.kernel.org
> Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Signed-off-by: Hans de Goede <hansg@kernel.org>
FWIW:
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> Changes in v2:
> - Fix typo in stable email address
> ---
> net/rfkill/rfkill-gpio.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/rfkill/rfkill-gpio.c b/net/rfkill/rfkill-gpio.c
> index 41e657e97761..cf2dcec6ce5a 100644
> --- a/net/rfkill/rfkill-gpio.c
> +++ b/net/rfkill/rfkill-gpio.c
> @@ -94,10 +94,10 @@ static const struct dmi_system_id rfkill_gpio_deny_table[] = {
> static int rfkill_gpio_probe(struct platform_device *pdev)
> {
> struct rfkill_gpio_data *rfkill;
> - struct gpio_desc *gpio;
> + const char *type_name = NULL;
> const char *name_property;
> const char *type_property;
> - const char *type_name;
> + struct gpio_desc *gpio;
> int ret;
>
> if (dmi_check_system(rfkill_gpio_deny_table))
> --
> 2.51.0
--
heikki
prev parent reply other threads:[~2025-09-15 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 11:35 [PATCH v2] net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer Hans de Goede
2025-09-15 12:24 ` Heikki Krogerus [this message]
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=aMgFa9LLJBhjcgJr@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=hansg@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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