From: Akihiro TSUKADA <tskd08@gmail.com>
To: Colin Ian King <colin.king@canonical.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
linux-media@vger.kernel.org, Antti Palosaari <crope@iki.fi>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: media: dvb-usb-v2/gl861: ensure USB message buffers DMA'able
Date: Tue, 3 Jul 2018 21:07:07 +0900 [thread overview]
Message-ID: <d2465376-4b3e-7d3d-86d2-0cd8d7543520@gmail.com> (raw)
In-Reply-To: <8308d9f0-2257-101c-69e3-8fe165de9348@canonical.com>
Hi,
thanks for the report.
> 47 buf = NULL;
>
> Condition rlen > 0, taking false branch.
>
> 48 if (rlen > 0) {
> 49 buf = kmalloc(rlen, GFP_KERNEL);
> 50 if (!buf)
> 51 return -ENOMEM;
> 52 }
>
> 53 usleep_range(1000, 2000); /* avoid I2C errors */
> 54
> CID 1470241 (#1 of 1): Explicit null dereferenced (FORWARD_NULL).
> var_deref_model: Passing null pointer buf to usb_control_msg, which
> dereferences it.
>
> 55 ret = usb_control_msg(d->udev, usb_rcvctrlpipe(d->udev, 0),
> req, type,
> 56 value, index, buf, rlen, 2000);
>
>
> The assignment of buf = NULL means a null buffer is passed down the usb
> control message stack until it eventually gets dereferenced. This only
> occurs when rlen <= 0. I was unsure how to fix this for the case when
> rlen <= 0, so I am flagging this up as an issue that needs fixing.
>
Since rlen is an u16, null pointer is passed only when rlen == 0,
so I think it is not a problem,
but I am OK to add a guard in order to make scan result clean.
regards,
Akihiro
next prev parent reply other threads:[~2018-07-03 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 12:58 Colin Ian King
2018-07-03 12:07 ` Akihiro TSUKADA [this message]
2018-07-25 13:57 ` Mauro Carvalho Chehab
2018-07-27 2:00 ` Akihiro TSUKADA
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=d2465376-4b3e-7d3d-86d2-0cd8d7543520@gmail.com \
--to=tskd08@gmail.com \
--cc=colin.king@canonical.com \
--cc=crope@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@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
Powered by JetHome