From: Helge Deller <deller@gmx.de>
To: Michael Buesch <mb@bu3sch.de>
Cc: kyle@mcmartin.ca, linux-parisc@vger.kernel.org
Subject: Re: [PATCH] parisc-isa-eeprom: Fix loff_t usage
Date: Wed, 05 Aug 2009 20:38:55 +0200 [thread overview]
Message-ID: <4A79D1BF.5020305@gmx.de> (raw)
In-Reply-To: <200907210058.44737.mb@bu3sch.de>
On 07/21/2009 12:58 AM, Michael Buesch wrote:
> loff_t is a signed type. If userspace passes a negative ppos, the "count"
> range check is weakened. "count"s bigger than HPEE_MAX_LENGTH will pass the check.
> Also, if ppos is negative, the readb(eisa_eeprom_addr + *ppos) will poke in random
> memory.
>
> Signed-off-by: Michael Buesch<mb@bu3sch.de>
> Cc: stable@kernel.org
Thanks!
Applied and pushed upstream.
Helge
> Patch is untested due to lack of hardware.
>
> ---
> drivers/parisc/eisa_eeprom.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-2.6.orig/drivers/parisc/eisa_eeprom.c
> +++ linux-2.6/drivers/parisc/eisa_eeprom.c
> @@ -48,21 +48,21 @@ static loff_t eisa_eeprom_llseek(struct
> return (offset>= 0&& offset< HPEE_MAX_LENGTH) ? (file->f_pos = offset) : -EINVAL;
> }
>
> static ssize_t eisa_eeprom_read(struct file * file,
> char __user *buf, size_t count, loff_t *ppos )
> {
> unsigned char *tmp;
> ssize_t ret;
> int i;
>
> - if (*ppos>= HPEE_MAX_LENGTH)
> + if (*ppos< 0 || *ppos>= HPEE_MAX_LENGTH)
> return 0;
>
> count = *ppos + count< HPEE_MAX_LENGTH ? count : HPEE_MAX_LENGTH - *ppos;
> tmp = kmalloc(count, GFP_KERNEL);
> if (tmp) {
> for (i = 0; i< count; i++)
> tmp[i] = readb(eisa_eeprom_addr+(*ppos)++);
>
> if (copy_to_user (buf, tmp, count))
> ret = -EFAULT;
>
next prev parent reply other threads:[~2009-08-05 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 22:58 [PATCH] parisc-isa-eeprom: Fix loff_t usage Michael Buesch
2009-08-05 18:38 ` Helge Deller [this message]
2009-08-05 19:57 ` James Bottomley
2009-08-05 20:14 ` Kyle McMartin
2009-08-05 20:20 ` Matthew Wilcox
2009-08-05 20:37 ` Kyle McMartin
2009-08-05 21:27 ` John David Anglin
2009-08-05 22:21 ` Helge Deller
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=4A79D1BF.5020305@gmx.de \
--to=deller@gmx.de \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).