WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH][cpufreq] add bounds checking for getcpuidletime

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH][cpufreq] add bounds checking for getcpuidletime
From: "Mark Langsdorf" <mark.langsdorf@xxxxxxx>
Date: Mon, 3 Dec 2007 10:48:42 -0600
Delivery-date: Mon, 03 Dec 2007 08:46:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6 (enterprise 20070904.708012)
The Xen platform hypercall for getting the cpu idletime does not
check to make sure that all cpus in the map have indexes less 
than the size of the array that it writes the data into.  Add
bounds checking to avoid memory corruption.

Signed-off-by: Mark Langsdorf <mark.langsdorf@xxxxxxx>

diff -r d40788f07a4f xen/arch/x86/platform_hypercall.c
--- a/xen/arch/x86/platform_hypercall.c Sun Nov 25 12:43:13 2007 +0000
+++ b/xen/arch/x86/platform_hypercall.c Mon Dec 03 10:25:23 2007 -0600
@@ -326,6 +326,9 @@ ret_t do_platform_op(XEN_GUEST_HANDLE(xe
                 cpu_clear(cpu, cpumap);
             }
 
+            if (cpu >= ctlmap.nr_cpus) 
+                continue;
+
             ret = -EFAULT;
             if ( copy_to_guest_offset(idletimes, cpu, &idletime, 1) )
                 goto out;



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>