From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Udipto Goswami <quic_ugoswami@quicinc.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: core: Prevent null pointer dereference in update_port_device_state
Date: Thu, 4 Jan 2024 14:13:51 +0100 [thread overview]
Message-ID: <2024010432-fifth-shakable-0d84@gregkh> (raw)
In-Reply-To: <eade09eb-4454-460f-9ce6-87da986c5acf@quicinc.com>
On Thu, Jan 04, 2024 at 06:35:38PM +0530, Udipto Goswami wrote:
> Hi Greg,
>
> On 1/4/2024 4:14 PM, Greg Kroah-Hartman wrote:
> > On Thu, Jan 04, 2024 at 03:56:16PM +0530, Udipto Goswami wrote:
> > > Currently,the function update_port_device_state gets the usb_hub from
> > > udev->parent by calling usb_hub_to_struct_hub.
> > > However, in case the actconfig or the maxchild is 0, the usb_hub would
> > > be NULL and upon further accessing to get port_dev would result in null
> > > pointer dereference.
> >
> > Is this true for any real (or fake) hardware?
>
> We saw this in our QCOM hardwares where lvstest.c was calling
> get_dev_desc_store:
>
> usb_set_device_state+0x128/0x17c
> create_lvs_device+0x60/0xf8 [lvstest]
> get_dev_desc_store+0x94/0x18c [lvstest]
> dev_attr_store+0x30/0x48
>
> I think the part of the test procedure is to first unbind the hub driver
> which calls hub_disconnect setting the maxchild = 0.
Are you sure lvstest is correct here?
thanks,
greg k-h
next prev parent reply other threads:[~2024-01-04 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 10:26 [PATCH] usb: core: Prevent null pointer dereference in update_port_device_state Udipto Goswami
2024-01-04 10:44 ` Greg Kroah-Hartman
2024-01-04 13:05 ` Udipto Goswami
2024-01-04 13:13 ` Greg Kroah-Hartman [this message]
2024-01-04 14:56 ` Alan Stern
2024-01-08 4:50 ` Udipto Goswami
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=2024010432-fifth-shakable-0d84@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_ugoswami@quicinc.com \
--cc=stern@rowland.harvard.edu \
/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