On Sat, 01 Aug 2009, Michael Buesch wrote:
> On Saturday 01 August 2009 17:04:19 Henrique de Moraes Holschuh wrote:
> > From: Michael Buesch <mb@xxxxxxxxx>
> >
> > Avoid a heap buffer overrun triggered by an integer overflow of the
> > userspace controlled "count" variable.
> >
> > If userspace passes in a "count" of (size_t)-1l, the kmalloc size will
> > overflow to ((size_t)-1l + 2) = 1, so only one byte will be allocated.
> > However, copy_from_user() will attempt to copy 0xFFFFFFFF (or
> > 0xFFFFFFFFFFFFFFFF on 64bit) bytes to the buffer.
> >
> > A possible testcase could look like this:
> >
> > #include <stdio.h>
> > #include <stdlib.h>
> > #include <unistd.h>
> > #include <fcntl.h>
> >
> > int main(int argc, char **argv)
> > {
> > int fd;
> > char c;
> >
> > if (argc != 2) {
> > printf("Usage: %s /proc/acpi/ibm/filename\n", argv[0]);
> > return 1;
> > }
> > fd = open(argv[1], O_RDWR);
> > if (fd < 0) {
> > printf("Could not open proc file\n");
> > return 1;
> > }
> > write(fd, &c, (size_t)-1l);
> > }
> >
> > We avoid the integer overrun by putting an arbitrary limit on the count.
> > PAGE_SIZE sounds like a sane limit.
> >
> > (note: this bug exists at least since kernel 2.6.12...)
> >
> > Signed-off-by: Michael Buesch <mb@xxxxxxxxx>
> > Acked-by: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
> > Cc: stable@xxxxxxxxxx
> > ---
> > drivers/platform/x86/thinkpad_acpi.c | 2 ++
> > 1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c
> > index 27d68e7..18f9ee6 100644
> > --- a/drivers/platform/x86/thinkpad_acpi.c
> > +++ b/drivers/platform/x86/thinkpad_acpi.c
> > @@ -766,6 +766,8 @@ static int dispatch_procfs_write(struct file *file,
> >
> > if (!ibm || !ibm->write)
> > return -EINVAL;
> > + if (count > PAGE_SIZE - 2)
> > + return -EINVAL;
> >
> > kernbuf = kmalloc(count + 2, GFP_KERNEL);
> > if (!kernbuf)
>
> Note that it turns out this is not a real-life bug after all.
> The VFS code checks count for signedness (high bit set) and bails
> out if this is the case.
> Well, it might probably be a good idea to restrict the count range to
> something sane here anyway, so...
It is a good idea to restrict the maximum size to something sane anyway.
But the commit message needs to be fixed if there is no security hole.
Anyway, in which function and file is the VFS code that restricts the
maximum size?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
