From: Johan Hovold <johan@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/7] Input: fix NULL-derefs at probe
Date: Mon, 13 Mar 2017 13:35:32 +0100 [thread overview]
Message-ID: <20170313123539.28103-1-johan@kernel.org> (raw)
This series fixes a number of NULL-pointer dereferences due to missing
endpoint sanity checks that can be triggered by a malicious USB device.
Johan
Johan Hovold (7):
Input: iforce - fix NULL-deref at probe
Input: cm109 - fix NULL-deref at probe
Input: ims-pcu - fix NULL-deref at probe
Input: yealink - fix NULL-deref at probe
Input: hanwang - fix NULL-deref at probe
Input: kbtab - fix NULL-deref at probe
Input: sur40 - fix NULL-deref at probe
drivers/input/joystick/iforce/iforce-usb.c | 3 +++
drivers/input/misc/cm109.c | 4 ++++
drivers/input/misc/ims-pcu.c | 4 ++++
drivers/input/misc/yealink.c | 4 ++++
drivers/input/tablet/hanwang.c | 3 +++
drivers/input/tablet/kbtab.c | 3 +++
drivers/input/touchscreen/sur40.c | 3 +++
7 files changed, 24 insertions(+)
--
2.12.0
next reply other threads:[~2017-03-13 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 12:35 Johan Hovold [this message]
2017-03-13 12:35 ` [PATCH 1/7] Input: iforce - fix NULL-deref at probe Johan Hovold
2017-03-13 12:35 ` [PATCH 2/7] Input: cm109 " Johan Hovold
2017-03-13 12:35 ` [PATCH 3/7] Input: ims-pcu " Johan Hovold
2017-03-13 12:35 ` [PATCH 4/7] Input: yealink " Johan Hovold
2017-03-13 12:35 ` [PATCH 5/7] Input: hanwang " Johan Hovold
2017-03-13 12:35 ` [PATCH 6/7] Input: kbtab " Johan Hovold
2017-03-13 12:35 ` [PATCH 7/7] Input: sur40 " Johan Hovold
2017-03-13 15:15 ` [PATCH 0/7] Input: fix NULL-derefs " Oliver Neukum
2017-03-13 15:45 ` Johan Hovold
2017-03-16 22:37 ` Dmitry Torokhov
2017-03-17 10:53 ` Johan Hovold
2017-03-17 21:03 ` Dmitry Torokhov
2017-03-18 9:13 ` Johan Hovold
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=20170313123539.28103-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).