| commit | 1b4f3a211878328065ee7ae79a380241bedaef5a | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Fri, 4 Nov 2011 18:24:08 +0000 (4 21:24 +0300) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Mon, 21 Nov 2011 22:35:26 +0000 (21 14:35 -0800) | ||
| tree | 61643564605ee122f710ae68c7abe9d68006208c | treesnapshot (tar.gz zip) |
| parent | 14fa9e2f0916742bf436e84895a3523551d325f5 | commitdiff |
xen-gntalloc: integer overflow in gntalloc_ioctl_alloc()
commit 21643e69a4c06f7ef155fbc70e3fba13fba4a756 upstream.
On 32 bit systems a high value of op.count could lead to an integer
overflow in the kzalloc() and gref_ids would be smaller than
expected. If the you triggered another integer overflow in
"if (gref_size + op.count > limit)" then you'd probably get memory
corruption inside add_grefs().
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 21643e69a4c06f7ef155fbc70e3fba13fba4a756 upstream.
On 32 bit systems a high value of op.count could lead to an integer
overflow in the kzalloc() and gref_ids would be smaller than
expected. If the you triggered another integer overflow in
"if (gref_size + op.count > limit)" then you'd probably get memory
corruption inside add_grefs().
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/xen/gntalloc.c | diffblobblamehistory |