From: Manu Gautam <mgautam@codeaurora.org>
To: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
Cc: linux-usb@vger.kernel.org, linux-usb-owner@vger.kernel.org
Subject: usb: gadget: composite: Fix double free memory bug
Date: Tue, 19 Mar 2019 14:33:11 +0530 [thread overview]
Message-ID: <91ee602fc4c76fec57a120c17186e67b@codeaurora.org> (raw)
Hi,
On 2019-03-15 16:37, Chandana Kishori Chiluveru wrote:
> configfs_dev_cleanup function can double free os_desc
> and buffer when called from different context. For
> example, this can be called from composite_unbind() and
> when composite_bind() fails.
Shouldn't we instead fix the error path handling of composite_bind
and configfs_composite_bind?
> Fix this issue by setting
> request and buffer pointer to NULL after kfree.
>
> Signed-off-by: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
> ---
> drivers/usb/gadget/composite.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/usb/gadget/composite.c
> b/drivers/usb/gadget/composite.c
> index b8a1584..992f1e2 100644
> --- a/drivers/usb/gadget/composite.c
> +++ b/drivers/usb/gadget/composite.c
> @@ -2155,14 +2155,18 @@ void composite_dev_cleanup(struct
> usb_composite_dev *cdev)
> usb_ep_dequeue(cdev->gadget->ep0, cdev->os_desc_req);
>
> kfree(cdev->os_desc_req->buf);
> + cdev->os_desc_req->buf = NULL;
> usb_ep_free_request(cdev->gadget->ep0, cdev->os_desc_req);
> + cdev->os_desc_req = NULL;
Better to move os_desc_cleanup handling to a different function
say - composite_os_desc_req_cleanup (to match
composite_os_desc_req_prepare())
> }
> if (cdev->req) {
> if (cdev->setup_pending)
> usb_ep_dequeue(cdev->gadget->ep0, cdev->req);
>
> kfree(cdev->req->buf);
> + cdev->req->buf = NULL;
> usb_ep_free_request(cdev->gadget->ep0, cdev->req);
> + cdev->req = NULL;
> }
> cdev->next_string_id = 0;
> device_remove_file(&cdev->gadget->dev, &dev_attr_suspended);
next reply other threads:[~2019-03-19 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 9:03 Manu Gautam [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-15 11:07 usb: gadget: composite: Fix double free memory bug Chandana Kishori Chiluveru
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=91ee602fc4c76fec57a120c17186e67b@codeaurora.org \
--to=mgautam@codeaurora.org \
--cc=cchiluve@codeaurora.org \
--cc=linux-usb-owner@vger.kernel.org \
--cc=linux-usb@vger.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;
as well as URLs for NNTP newsgroup(s).