From: Gerd Hoffmann <kraxel@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qinghao Tang <luodalongde@gmail.com>,
Qemu Developers <qemu-devel@nongnu.org>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] usb: check RNDIS offsets & length
Date: Mon, 22 Feb 2016 09:39:50 +0100 [thread overview]
Message-ID: <1456130390.29896.30.camel@redhat.com> (raw)
In-Reply-To: <1455648821-17340-1-git-send-email-ppandit@redhat.com>
On Mi, 2016-02-17 at 00:23 +0530, P J P wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> Hello,
>
> When processing remote NDIS control message packets, the USB Net
> device emulator uses a fixed length(4096) data buffer. The incoming
> packet length could exceed that OR informationBufferOffset & Length
> combination could overflow and cross that range. These two patches
> add checks to avoid such overflows.
Added both to usb patch queue.
thanks,
Gerd
prev parent reply other threads:[~2016-02-22 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 18:53 [Qemu-devel] [PATCH 0/2] usb: check RNDIS offsets & length P J P
2016-02-16 18:53 ` [Qemu-devel] [PATCH 1/2] usb: check RNDIS message length P J P
2016-02-16 18:53 ` [Qemu-devel] [PATCH 2/2] usb: check RNDIS buffer offsets & length P J P
2016-02-22 8:39 ` Gerd Hoffmann [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=1456130390.29896.30.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=luodalongde@gmail.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.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).