From: Maxim Korotkov <korotkov.maxim.s@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] usb: typec: fix potential NULL dereference
Date: Tue, 18 Apr 2023 09:56:51 +0300 [thread overview]
Message-ID: <22a5bd86-8d41-14e2-bb5a-968d15618adf@gmail.com> (raw)
In-Reply-To: <ZD41tLi3sMB71Xf2@kroah.com>
On 18.04.2023 09:16, Greg Kroah-Hartman wrote:
> On Mon, Apr 17, 2023 at 10:50:03PM +0300, Maxim Korotkov wrote:
>> The pointer 'adev' was being dereferenced before being checked for NULL
>> in the 'type_alt mode_enter()' and 'type_alt mode_exit()' functions.
>> Although this is a hypothetical issue, it's better to move the pointer
>> assignment after the NULL check to avoid any potential problems.
>>
>> Found by Linux Verification Center with Svace static analyzer.
>>
>> Fixes: 8a37d87d72f0 ("usb: typec: Bus type for alternate modes")
>> Signed-off-by: Maxim Korotkov <korotkov.maxim.s@gmail.com>
>> ---
>> drivers/usb/typec/bus.c | 13 +++++++++----
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/usb/typec/bus.c b/drivers/usb/typec/bus.c
>> index 098f0efaa58d..ae0aca8f33db 100644
>> --- a/drivers/usb/typec/bus.c
>> +++ b/drivers/usb/typec/bus.c
>> @@ -125,13 +125,16 @@ EXPORT_SYMBOL_GPL(typec_altmode_notify);
>> */
>> int typec_altmode_enter(struct typec_altmode *adev, u32 *vdo)
>> {
>> - struct altmode *partner = to_altmode(adev)->partner;
>> - struct typec_altmode *pdev = &partner->adev;
>> + struct altmode *partner;
>> + struct typec_altmode *pdev;
>> int ret;
>>
>> if (!adev || adev->active)
>> return 0;
>>
>> + partner = to_altmode(adev)->partner;
>> + pdev = &partner->adev;
>
> As you point out, the original code is still fine here, we check before
> we actually use these values.
>
> Also, can adev every actually be NULL? In looking at the code paths, I
> can't see how that could happen.
>
> thanks,
>
> greg k-h
I agree that the adev will most likely never be NULL, but usually this
pointer is checked before usage (for example in typec_altmode_notify()
or typec_altmode_vdm()). It is a little odd that in these functions it
utilized before check. Is it just extra check that can be removed?
best regards, Max
next prev parent reply other threads:[~2023-04-18 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 19:50 [PATCH] usb: typec: fix potential NULL dereference Maxim Korotkov
2023-04-18 6:16 ` Greg Kroah-Hartman
2023-04-18 6:56 ` Maxim Korotkov [this message]
2023-04-20 8:39 ` Heikki Krogerus
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=22a5bd86-8d41-14e2-bb5a-968d15618adf@gmail.com \
--to=korotkov.maxim.s@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lvc-project@linuxtesting.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