All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Malone <peter.malone@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH]        Fixing arbitrary kernel leak in case FBIOGETCMAP_SPARC in sbusfb_ioctl_helper().
Date: Tue, 30 Jan 2018 20:30:42 +0000	[thread overview]
Message-ID: <20180130203042.4797-1-peter.malone@gmail.com> (raw)

Signed-off-by: Peter Malone <peter.malone@gmail.com>
---
 drivers/video/fbdev/sbuslib.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/video/fbdev/sbuslib.c b/drivers/video/fbdev/sbuslib.c
index af6fc97f4ba4..a436d44f1b7f 100644
--- a/drivers/video/fbdev/sbuslib.c
+++ b/drivers/video/fbdev/sbuslib.c
@@ -122,7 +122,7 @@ int sbusfb_ioctl_helper(unsigned long cmd, unsigned long arg,
 		unsigned char __user *ured;
 		unsigned char __user *ugreen;
 		unsigned char __user *ublue;
-		int index, count, i;
+		unsigned int index, count, i;
 
 		if (get_user(index, &c->index) ||
 		    __get_user(count, &c->count) ||
@@ -161,7 +161,7 @@ int sbusfb_ioctl_helper(unsigned long cmd, unsigned long arg,
 		unsigned char __user *ugreen;
 		unsigned char __user *ublue;
 		struct fb_cmap *cmap = &info->cmap;
-		int index, count, i;
+		unsigned int index, count, i;
 		u8 red, green, blue;
 
 		if (get_user(index, &c->index) ||
-- 
2.14.3


             reply	other threads:[~2018-01-30 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 20:30 Peter Malone [this message]
2018-01-31  8:33 ` [PATCH] Fixing arbitrary kernel leak in case FBIOGETCMAP_SPARC in sbusfb_ioctl_helper() Mathieu Malaterre
2018-01-31  8:33   ` Mathieu Malaterre
2018-01-31 14:57 ` [PATCH v2] " Peter Malone
2018-01-31 15:49   ` Mathieu Malaterre
2018-01-31 15:49     ` Mathieu Malaterre
2018-02-04 14:12     ` Peter Malone
2018-02-04 14:18     ` Peter Malone
2018-02-04 14:18       ` Peter Malone
2018-03-07 13:03       ` Bartlomiej Zolnierkiewicz
2018-03-07 13:03         ` Bartlomiej Zolnierkiewicz

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=20180130203042.4797-1-peter.malone@gmail.com \
    --to=peter.malone@gmail.com \
    --cc=linux-fbdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.