From: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: PATCH: 2.6.7-rc3 drivers/video/fbmem.c: user/kernel pointer bugs
Date: 09 Jun 2004 15:46:39 -0700 [thread overview]
Message-ID: <1086821199.32054.111.camel@dooby.cs.berkeley.edu> (raw)
Since sprite is a user pointer, reading sprite->mask or sprite->image.data
requires unsafe dereferences. Let me know if you have any questions or if
I've made a mistake.
Best,
Rob
--- linux-2.6.7-rc3-full/drivers/video/fbmem.c.orig Wed Jun 9 13:09:30 2004
+++ linux-2.6.7-rc3-full/drivers/video/fbmem.c Wed Jun 9 13:07:06 2004
@@ -901,7 +901,9 @@ fb_cursor(struct fb_info *info, struct f
{
struct fb_cursor cursor;
int err;
-
+ char *mask;
+ const char *image_data;
+
if (copy_from_user(&cursor, sprite, sizeof(struct fb_cursor)))
return -EFAULT;
@@ -920,18 +922,20 @@ fb_cursor(struct fb_info *info, struct f
(cursor.image.width != info->cursor.image.width))
cursor.set |= FB_CUR_SETSIZE;
+ image_data = cursor.image.data;
cursor.image.data = kmalloc(size, GFP_KERNEL);
if (!cursor.image.data)
return -ENOMEM;
+ mask = cursor.mask;
cursor.mask = kmalloc(size, GFP_KERNEL);
if (!cursor.mask) {
kfree(cursor.image.data);
return -ENOMEM;
}
- if (copy_from_user(cursor.image.data, sprite->image.data, size) ||
- copy_from_user(cursor.mask, sprite->mask, size)) {
+ if (copy_from_user(cursor.image.data, image_data, size) ||
+ copy_from_user(cursor.mask, mask, size)) {
kfree(cursor.image.data);
kfree(cursor.mask);
return -EFAULT;
next reply other threads:[~2004-06-09 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 22:46 Robert T. Johnson [this message]
2004-06-10 1:24 ` PATCH: 2.6.7-rc3 drivers/video/fbmem.c: user/kernel pointer bugs viro
2004-06-10 3:50 ` Robert T. Johnson
2004-06-10 4:15 ` viro
2004-06-10 5:00 ` Robert T. Johnson
2004-06-10 9:15 ` Geert Uytterhoeven
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=1086821199.32054.111.camel@dooby.cs.berkeley.edu \
--to=rtjohnso@eecs.berkeley.edu \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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).