From: Lee Jones <lee@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-leds@vger.kernel.org, "Pavel Machek" <pavel@kernel.org>,
"Marek Behún" <kabel@kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] leds: is31fl32xx: Fix NULL pointer dereference when binding via I2C ID table
Date: Fri, 16 Oct 2026 09:16:10 +0100 [thread overview]
Message-ID: <20261016081610.GA2663669@google.com> (raw)
In-Reply-To: <179198424632.839288.1637324900719734962@kernel.org>
On Mon, 05 Oct 2026, Lee Jones wrote:
> --- checkpatch.pl: clean (0 issues) ---
>
> On Mon, 05 Oct 2026, Rosen Penev wrote:
>
> > If the device binds via the I2C ID table (e.g., fallback matching by
> > node name, sysfs new_device, or software node),
> > device_get_match_data() in is31fl32xx_probe() returns NULL because
> > the is31fl32xx_id table entries have no .driver_data.
> >
> > Without a NULL check, is31fl32xx_parse_dt() will unconditionally
> > dereference cdef when checking cdef->output_frequency_setting_reg,
> > and is31fl32xx_parse_child_dt() will dereference cdef->channels,
> > leading to a NULL pointer dereference and kernel oops.
> >
> > Add a NULL check for cdef alongside the existing child count check in
> > is31fl32xx_probe(), returning -EINVAL if no match data is available.
> >
> > Fixes: 2779f4724b2f ("leds: various: use device_get_match_data")
> > Cc: stable@vger.kernel.org
> > Assisted-by: LLM
> > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> > ---
> > drivers/leds/leds-is31fl32xx.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/leds/leds-is31fl32xx.c b/drivers/leds/leds-is31fl32xx.c
> > index 285085d27453..7bb0295b0b49 100644
> > --- a/drivers/leds/leds-is31fl32xx.c
> > +++ b/drivers/leds/leds-is31fl32xx.c
> > @@ -577,7 +577,7 @@ static int is31fl32xx_probe(struct i2c_client *client)
> > cdef = device_get_match_data(dev);
> >
> > count = device_get_child_node_count(dev);
> > - if (!count)
> > + if (!cdef || !count)
> > return -EINVAL;
If it's possible for devices to be autoloaded via is31fl32xx_id,
wouldn't it make more sense to populate its .driver_data instead?
Or, if that's not possible for some odd reason (which you must specify),
since this is an || it's odd to check the return values like this. It
more inline with current coding guidelines to place the check below its
caller / allocator.
> > priv = devm_kzalloc(dev, struct_size(priv, leds, count),
> > --
> > 2.56.0
> >
>
> --
> Lee Jones
--
Lee Jones
prev parent reply other threads:[~2026-10-16 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 19:49 [PATCH] leds: is31fl32xx: Fix NULL pointer dereference when binding via I2C ID table Rosen Penev
2026-10-05 19:56 ` sashiko-bot
2026-10-08 7:49 ` Griffin Kroah-Hartman
[not found] ` <179198424632.839288.1637324900719734962@kernel.org>
2026-10-16 8:16 ` Lee Jones [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=20261016081610.GA2663669@google.com \
--to=lee@kernel.org \
--cc=kabel@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rosenp@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