[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <371E240E6FC1D44DA5E51EE9DCDCB7840105CB22F2@NA-MBX-01.mgc.mentorg.com>
Date: Tue, 20 Jan 2015 15:23:19 +0000
From: "Mehaffey, John" <John_Mehaffey@...tor.com>
To: "oss-security@...ts.openwall.com" <oss-security@...ts.openwall.com>
Subject: RE: CVE Request: Linux kernel information leak in
event device handling
> From: Marcus Meissner [meissner@...e.de]
> Sent: Tuesday, January 20, 2015 6:43 AM
> To: OSS Security List
> Subject: [oss-security] CVE Request: Linux kernel information leak in event device handling
>
> Hi,
>
> This needs a CVE, information leak out of the kernel.
>
> This probably was introduced by commit 483180281f0ac60d1138710eb21f4b9961901294
> in Linux 3.9.
>
> Ciao, Marcus
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7c4f56070fde2367766fa1fb04852599b5e1ad35
> https://bugzilla.suse.com/show_bug.cgi?id=904899
>
> Input: evdev - fix EVIOCG{type} ioctl
>
> The 'max' size passed into the function is measured in number of bits
> (KEY_MAX, LED_MAX, etc) so we need to convert it accordingly before
> trying to copy the data out, otherwise we will try copying too much
> and end up with up with a page fault.
>
> Reported-by: Pavel Machek <pavel@....cz>
> Reviewed-by: Pavel Machek <pavel@....cz>
> Reviewed-by: David Herrmann <dh.herrmann@...il.com>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
I don't see how this could leak information to the user.
Without the patch, too much memory is allocated internally in the driver, and too much data is copied into that buffer (potentially causing a page fault) but the same, correct amount of data is copied out to the user both before and after this patch.
Sincerely,
John Mehaffey
Linux System Architect
Mentor Graphics
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
