From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+6c7e68b141ebd3a2cadf@syzkaller.appspotmail.com
Subject: Re: [PATCH] usb: typec: stusb160x: add missing NULL check for i2c_get_match_data()
Date: Mon, 24 Aug 2026 08:45:59 +0200 [thread overview]
Message-ID: <2026082403-decathlon-produce-b31f@gregkh> (raw)
In-Reply-To: <20260824084041.0000295f@gmail.com>
On Mon, Aug 24, 2026 at 08:40:41AM +0200, Joshua Crofts wrote:
> On Thu, 6 Aug 2026 08:43:01 +0000
> Joshua Crofts <joshua.crofts1@gmail.com> wrote:
>
> > In stusb160x_probe(), the return value of i2c_get_match_data() is not
> > checked, causing a null pointer dereference later on if the device was
> > registered manually (without devicetree or ACPI).
> >
> > Fix this by adding a NULL check for the return value of
> > i2c_get_match_data().
> >
> > Reported-by: syzbot+6c7e68b141ebd3a2cadf@syzkaller.appspotmail.com
> > Closes: https://syzkaller.appspot.com/bug?extid=6c7e68b141ebd3a2cadf
> > Fixes: 823754697556 ("usb: typec: stusb160x: Make use of i2c_get_match_data()")
> > Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
> > ---
> > drivers/usb/typec/stusb160x.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/usb/typec/stusb160x.c b/drivers/usb/typec/stusb160x.c
> > index 6d85b25b40bc..8f3435c669cd 100644
> > --- a/drivers/usb/typec/stusb160x.c
> > +++ b/drivers/usb/typec/stusb160x.c
> > @@ -645,6 +645,8 @@ static int stusb160x_probe(struct i2c_client *client)
> > i2c_set_clientdata(client, chip);
> >
> > regmap_config = i2c_get_match_data(client);
> > + if (!regmap_config)
> > + return -ENODEV;
> >
> > chip->regmap = devm_regmap_init_i2c(client, regmap_config);
> > if (IS_ERR(chip->regmap)) {
>
> Hi Greg and Heikki,
>
> A (very) gentle ping on this patch. Do you need a v2 to include the
It's the middle of the merge window, we can't do anything until -rc1 is
out.
Also, this patch really isn't even needed, just don't attempt to bind
drivers to devices that are not the correct device.
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-24 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:43 Joshua Crofts
2026-08-06 8:47 ` Joshua Crofts
2026-08-24 6:40 ` Joshua Crofts
2026-08-24 6:45 ` Greg Kroah-Hartman [this message]
2026-08-24 6:48 ` Andy Shevchenko
2026-08-24 7:04 ` Joshua Crofts
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=2026082403-decathlon-produce-b31f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+6c7e68b141ebd3a2cadf@syzkaller.appspotmail.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®