We cap "stat.size" at INT_MAX but we don't check for negative values so
my static checker complains. At this point, you already have control of
the kernel and if you start passing negative values here then you
deserve what happens next.
On 64 bit systems the vmalloc() will definitely fail. On 32 bit systems
we truncate the upper 32 bits away so that could succeed. I haven't
followed it further than that.
Signed-off-by: Dan Carpenter <dan.carpen...@oracle.com>
diff --git a/kernel/module.c b/kernel/module.c
index 626d164..26e0d15 100644
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -2536,7 +2536,7 @@ static int copy_module_from_fd(int fd, struct load_info
*info)
}
/* Don't hand 0 to vmalloc, it whines. */
- if (stat.size == 0) {
+ if (stat.size <= 0) {
err = -EINVAL;
goto out;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
