From: Felipe Balbi <balbi@kernel.org>
To: Peter Chen <peter.chen@nxp.com>, Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: "gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"pawell\@cadence.com" <pawell@cadence.com>,
"rogerq\@ti.com" <rogerq@ti.com>,
"colin.king\@canonical.com" <colin.king@canonical.com>,
"yuehaibing\@huawei.com" <yuehaibing@huawei.com>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: cdns3: fix possible buffer overflow caused by bad DMA value
Date: Wed, 01 Jul 2020 09:52:43 +0300 [thread overview]
Message-ID: <87366b916s.fsf@kernel.org> (raw)
In-Reply-To: <20200601041048.GB13752@b29397-desktop>
[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]
Peter Chen <peter.chen@nxp.com> writes:
> On 20-05-30 11:24:00, Jia-Ju Bai wrote:
>> In cdns3_ep0_setup_phase():
>> struct usb_ctrlrequest *ctrl = priv_dev->setup_buf;
>>
>> Because priv_dev->setup_buf (allocated in cdns3_gadget_start) is stored
>> in DMA memory, and thus ctrl is a DMA value.
>>
>> cdns3_ep0_setup_phase()
>> cdns3_ep0_standard_request(priv_dev, ctrl)
>> cdns3_req_ep0_get_status(priv_dev, ctrl)
>> index = cdns3_ep_addr_to_index(ctrl->wIndex);
>> priv_ep = priv_dev->eps[index];
>>
>> cdns3_ep0_setup_phase()
>> cdns3_ep0_standard_request(priv_dev, ctrl)
>> cdns3_req_ep0_handle_feature(priv_dev, ctrl_req, 0)
>> cdns3_ep0_feature_handle_endpoint(priv_dev, ctrl, set)
>> index = cdns3_ep_addr_to_index(ctrl->wIndex);
>> priv_ep = priv_dev->eps[index];
>>
>> In these cases, ctrl->wIndex can be be modified at anytime by malicious
>> hardware, and thus a buffer overflow can occur when the code
>> "priv_dev->eps[index]" is executed.
>>
>
> Did you see the setup buffer is overwritten before the setup handling is
> finished?
>
>> To fix these possible bugs, index is checked before being used.
>
> I think the better fix is to use one additional buffer for struct
> usb_ctrlrequest, and copy the dma_buf to it after setup packet
> has received, then use the value stored in this buffer for later
> operation, it could avoid quitting the code which is useful in fact.
Why is this a better fix? If you don't have that endpoint index, you
shouldn't try to access it. However, I think the problem here is
slightly easier to solve :-)
>> diff --git a/drivers/usb/cdns3/ep0.c b/drivers/usb/cdns3/ep0.c
>> index e71240b386b4..0a80c7ade613 100644
>> --- a/drivers/usb/cdns3/ep0.c
>> +++ b/drivers/usb/cdns3/ep0.c
>> @@ -265,6 +265,8 @@ static int cdns3_req_ep0_get_status(struct cdns3_device *priv_dev,
>> return cdns3_ep0_delegate_req(priv_dev, ctrl);
>> case USB_RECIP_ENDPOINT:
>> index = cdns3_ep_addr_to_index(ctrl->wIndex);
diff --git a/drivers/usb/cdns3/gadget.c b/drivers/usb/cdns3/gadget.c
index 5e24c2e57c0d..96ba3eec805c 100644
--- a/drivers/usb/cdns3/gadget.c
+++ b/drivers/usb/cdns3/gadget.c
@@ -107,7 +107,10 @@ void cdns3_set_register_bit(void __iomem *ptr, u32 mask)
*/
u8 cdns3_ep_addr_to_index(u8 ep_addr)
{
- return (((ep_addr & 0x7F)) + ((ep_addr & USB_DIR_IN) ? 16 : 0));
+ u8 num = ep_addr & USB_ENDPOINT_NUMBER_MASK;
+ u8 dir = ep_addr & USB_ENDPOINT_DIR_MASK;
+
+ return num + dir ? 16 : 0;
}
static int cdns3_get_dma_pos(struct cdns3_device *priv_dev,
This will guarantee that the number is never over the limit.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-07-01 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 3:24 [PATCH] usb: cdns3: fix possible buffer overflow caused by bad DMA value Jia-Ju Bai
2020-06-01 4:10 ` Peter Chen
2020-07-01 6:52 ` Felipe Balbi [this message]
2020-07-01 8:31 ` Peter Chen
-- strict thread matches above, loose matches on Subject: below --
2020-05-30 9:24 Markus Elfring
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=87366b916s.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=peter.chen@nxp.com \
--cc=rogerq@ti.com \
--cc=yuehaibing@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).