From: Shuah Khan <skhan@linuxfoundation.org>
To: Greg KH <gregkh@linuxfoundation.org>,
longlong yan <yanlonglong@kylinos.cn>
Cc: valentina.manea.m@gmail.com, shuah@kernel.org, i@zenithal.me,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] usb: usbip: add NULL check after calloc()
Date: Fri, 4 Sep 2026 11:07:18 -0600 [thread overview]
Message-ID: <2977dab3-70a3-45b3-ac08-41bc362121a2@linuxfoundation.org> (raw)
In-Reply-To: <2026090249-poking-monorail-0d2d@gregkh>
On 9/2/26 02:42, Greg KH wrote:
> On Wed, Sep 02, 2026 at 03:09:31PM +0800, longlong yan wrote:
>> Two calloc() calls in the usbip driver lack NULL return checks, leading
>> to potential NULL pointer dereferences on allocation failure:
>
> This is in userspace, not in the "driver".
>
> And how do you get a failure for calloc() in userspace?
>
>> 1. usbipd.c do_standalone_mode(): the allocated `fds` array is
>> immediately dereferenced in the following for-loop via fds[i].fd
>> without checking for NULL.
>>
>> 2. usbip_host_common.c usbip_exported_device_new(): the allocated
>> `edev` is immediately dereferenced via edev->sudev without checking
>> for NULL.
>>
>> Add NULL checks after each calloc(), returning -1 in do_standalone_mode()
>> and using the existing goto err path in usbip_exported_device_new(),
>> consistent with the error handling already present in both functions.
>>
>> Signed-off-by: longlong yan <yanlonglong@kylinos.cn>
>> ---
>> tools/usb/usbip/libsrc/usbip_host_common.c | 2 ++
>> tools/usb/usbip/src/usbipd.c | 4 ++++
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/tools/usb/usbip/libsrc/usbip_host_common.c b/tools/usb/usbip/libsrc/usbip_host_common.c
>> index 01599cb2fa7b..8ad367e09e78 100644
>> --- a/tools/usb/usbip/libsrc/usbip_host_common.c
>> +++ b/tools/usb/usbip/libsrc/usbip_host_common.c
>> @@ -71,6 +71,8 @@ struct usbip_exported_device *usbip_exported_device_new(
>> int i;
>>
>> edev = calloc(1, sizeof(struct usbip_exported_device));
>> + if (!edev)
>> + goto err;
>>
>> edev->sudev =
>> udev_device_new_from_syspath(udev_context, sdevpath);
>> diff --git a/tools/usb/usbip/src/usbipd.c b/tools/usb/usbip/src/usbipd.c
>> index 3e22b651c754..cc707dea2882 100644
>> --- a/tools/usb/usbip/src/usbipd.c
>> +++ b/tools/usb/usbip/src/usbipd.c
>> @@ -544,6 +544,10 @@ static int do_standalone_mode(int daemonize, int ipv4, int ipv6)
>> dbg("listening on %d address%s", nsockfd, (nsockfd == 1) ? "" : "es");
>>
>> fds = calloc(nsockfd, sizeof(struct pollfd));
>> + if (!fds) {
>> + err("calloc for fds");
>> + return -1;
>
> I don't think you tested this :(
>
> You leak stuff here, right?
>
Thank you Greg for the review.
longlong yan, I am very reluctant to take usbip patches without
solid evidence of a real bug that can be reproduced and the patch
fixes it.
I am seeing a few too many usbip patches these days that don't fix
any bugs.
thanks,
-- Shuah
prev parent reply other threads:[~2026-09-04 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 7:09 [PATCH] usb: usbip: add NULL check after calloc() longlong yan
2026-09-02 8:42 ` Greg KH
2026-09-04 17:07 ` Shuah Khan [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=2977dab3-70a3-45b3-ac08-41bc362121a2@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=i@zenithal.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=valentina.manea.m@gmail.com \
--cc=yanlonglong@kylinos.cn \
/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