From: P J P <ppandit@redhat.com>
To: Qemu Developers <qemu-devel@nongnu.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <pmathieu@redhat.com>,
"Arash TC" <tohidi.arash@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v1] bt: use size_t type for length parameters instead of int
Date: Sat, 27 Oct 2018 01:19:53 +0530 (IST) [thread overview]
Message-ID: <nycvar.YSQ.7.76.1810270118190.7551@xnncv> (raw)
In-Reply-To: <20181021175858.25886-1-ppandit@redhat.com>
+-- On Sun, 21 Oct 2018, P J P wrote --+
| The length parameter values are not negative, thus use an unsigned
| type 'size_t' for them. Many routines pass 'len' values to memcpy(3)
| calls. If it was negative, it could lead to memory corruption issues.
| Add check to avoid it.
|
| Reported-by: Arash TC <tohidi.arash@gmail.com>
| Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
| ---
| bt-host.c | 8 +++---
| bt-vhci.c | 7 +++---
| hw/bt/core.c | 2 +-
| hw/bt/hci-csr.c | 20 +++++++--------
| hw/bt/hci.c | 38 ++++++++++++++--------------
| hw/bt/hid.c | 10 ++++----
| hw/bt/l2cap.c | 56 ++++++++++++++++++++++--------------------
| hw/bt/sdp.c | 6 ++---
| hw/usb/dev-bluetooth.c | 12 ++++-----
| include/hw/bt.h | 8 +++---
| include/sysemu/bt.h | 10 ++++----
| 11 files changed, 90 insertions(+), 87 deletions(-)
|
| Update v1: add assert check in vhci_host_send. Also check other places wherein
| length is used with fixed size buffers.
| -> https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg03831.html
Ping...!
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2018-10-26 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 17:58 [Qemu-devel] [PATCH v1] bt: use size_t type for length parameters instead of int P J P
2018-10-26 19:49 ` P J P [this message]
2018-11-02 9:05 ` P J P
2018-11-06 14:52 ` Thomas Huth
2018-11-06 15:26 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2018-11-06 18:56 ` [Qemu-devel] " Paolo Bonzini
2018-11-06 15:09 ` Philippe Mathieu-Daudé
2018-11-19 11:14 ` P J P
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=nycvar.YSQ.7.76.1810270118190.7551@xnncv \
--to=ppandit@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pmathieu@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tohidi.arash@gmail.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).