From: Johan Hovold <johan@kernel.org>
To: "Bence Csókás" <bence98@sch.bme.hu>
Cc: linux-i2c@vger.kernel.org, Andi Shyti <andi.shyti@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] i2c: cp2615: fix serial string NULL-deref at probe
Date: Thu, 12 Mar 2026 11:35:49 +0100 [thread overview]
Message-ID: <abKXBepGY2ha3DHc@hovoldconsulting.com> (raw)
In-Reply-To: <32f6793c-d728-451d-9e32-35d864fe0035@sch.bme.hu>
On Wed, Mar 11, 2026 at 10:40:19PM +0100, Bence Csókás wrote:
> Reviewed-by: Bence Csókás <bence98@sch.bme.hu>
>
> On 3/9/26 08:50, Johan Hovold wrote:
> > The cp2615 driver uses the USB device serial string as the i2c adapter
> > name but does not make sure that the string exists.
> >
> > Verify that the device has a serial number before accessing it to avoid
> > triggering a NULL-pointer dereference (e.g. with malicious devices).
> > @@ -297,6 +297,9 @@ cp2615_i2c_probe(struct usb_interface *usbif, const struct usb_device_id *id)
> > if (!adap)
> > return -ENOMEM;
> >
> > + if (!usbdev->serial)
> > + return -EINVAL;
> > +
> > strscpy(adap->name, usbdev->serial, sizeof(adap->name));
> > adap->owner = THIS_MODULE;
> > adap->dev.parent = &usbif->dev;
> AFAIK real CP2615s will always have a serial, so returning error should
> not be a major problem.
That's my reasoning as well. In the unlikely event that there'll ever be
valid firmware without a serial string we can amend the driver.
Johan
next prev parent reply other threads:[~2026-03-12 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 7:50 [PATCH] i2c: cp2615: fix serial string NULL-deref at probe Johan Hovold
2026-03-11 21:40 ` Bence Csókás
2026-03-12 10:35 ` Johan Hovold [this message]
2026-03-19 22:28 ` Andi Shyti
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=abKXBepGY2ha3DHc@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=bence98@sch.bme.hu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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