public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hemant Kumar <hemantk@codeaurora.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>,
	Bhaumik Bhatt <bbhatt@codeaurora.org>,
	mani@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/8] bus: mhi: core: Read transfer length from an event properly
Date: Wed, 29 Apr 2020 10:30:19 -0700	[thread overview]
Message-ID: <967ee378-bac9-32ba-0110-162dfdb71c1a@codeaurora.org> (raw)
In-Reply-To: <cbd0698d-52ca-fad6-a658-e6e0009bde66@codeaurora.org>

Hi Jeff

On 4/28/20 7:50 AM, Jeffrey Hugo wrote:
> On 4/27/2020 8:59 PM, Bhaumik Bhatt wrote:
>> From: Hemant Kumar <hemantk@codeaurora.org>
>>
>> When MHI Driver receives an EOT event, it reads xfer_len from the
>> event in the last TRE. The value is under control of the MHI device
>> and never validated by Host MHI driver. The value should never be
>> larger than the real size of the buffer but a malicious device can
>> set the value 0xFFFF as maximum. This causes device to memory
> 
> The device will overflow, or the driver?
Done.
> 
>> overflow (both read or write). Fix this issue by reading minimum of
>> transfer length from event and the buffer length provided.
>>
>> Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
>> Signed-off-by: Bhaumik Bhatt <bbhatt@codeaurora.org>
>> ---
>>   drivers/bus/mhi/core/main.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/bus/mhi/core/main.c b/drivers/bus/mhi/core/main.c
>> index 1ccd4cc..3d468d9 100644
>> --- a/drivers/bus/mhi/core/main.c
>> +++ b/drivers/bus/mhi/core/main.c
>> @@ -521,7 +521,10 @@ static int parse_xfer_event(struct mhi_controller 
>> *mhi_cntrl,
>>                   mhi_cntrl->unmap_single(mhi_cntrl, buf_info);
>>               result.buf_addr = buf_info->cb_buf;
>> -            result.bytes_xferd = xfer_len;
>> +
>> +            /* truncate to buf len if xfer_len is larger */
>> +            result.bytes_xferd =
>> +                min_t(u16, xfer_len, buf_info->len);
>>               mhi_del_ring_element(mhi_cntrl, buf_ring);
>>               mhi_del_ring_element(mhi_cntrl, tre_ring);
>>               local_rp = tre_ring->rp;
>>
> 
> 

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2020-04-29 17:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  2:59 [RESEND PATCH v2 0/8] Bug fixes and improved logging in MHI Bhaumik Bhatt
2020-04-28  2:59 ` [PATCH v2 1/8] bus: mhi: core: Cache intmod from mhi event to mhi channel Bhaumik Bhatt
2020-04-28 14:39   ` Jeffrey Hugo
2020-04-29 17:27     ` Hemant Kumar
2020-04-28  2:59 ` [PATCH v2 2/8] bus: mhi: core: Add range check for channel id received in event ring Bhaumik Bhatt
2020-04-28 14:44   ` Jeffrey Hugo
2020-04-29 17:29     ` Hemant Kumar
2020-04-28  2:59 ` [PATCH v2 3/8] bus: mhi: core: Read transfer length from an event properly Bhaumik Bhatt
2020-04-28 14:50   ` Jeffrey Hugo
2020-04-29 17:30     ` Hemant Kumar [this message]
2020-04-28  2:59 ` [PATCH v2 4/8] bus: mhi: core: Handle firmware load using state worker Bhaumik Bhatt
2020-04-28 14:27   ` Jeffrey Hugo
2020-04-28  2:59 ` [PATCH v2 5/8] bus: mhi: core: WARN_ON for malformed vector table Bhaumik Bhatt
2020-04-28  2:59 ` [PATCH v2 6/8] bus: mhi: core: Return appropriate error codes for AMSS load failure Bhaumik Bhatt
2020-04-28  2:59 ` [PATCH v2 7/8] bus: mhi: core: Improve debug logs for loading firmware Bhaumik Bhatt
2020-04-28  2:59 ` [PATCH v2 8/8] bus: mhi: core: Ensure non-zero session or sequence ID values Bhaumik Bhatt

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=967ee378-bac9-32ba-0110-162dfdb71c1a@codeaurora.org \
    --to=hemantk@codeaurora.org \
    --cc=bbhatt@codeaurora.org \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@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