First published: Mon Nov 08 2010(Updated: )
Description of problem: gdth_ioctl_alloc() takes the size variable as an int. copy_from_user() takes the size variable as an unsigned long. gen.data_len and gen.sense_len are unsigned longs. On x86_64 longs are 64 bit and ints are 32 bit. We could pass in a very large number and the allocation would truncate the size to 32 bits and allocate a small buffer. Then when we do the copy_from_user(), it would result in a memory corruption. Reference: <a href="http://ns3.spinics.net/lists/linux-scsi/msg47361.html">http://ns3.spinics.net/lists/linux-scsi/msg47361.html</a> Upstream: <a href="http://git.kernel.org/linus/f63ae56e4e97fb12053590e41a4fa59e7daa74a4">http://git.kernel.org/linus/f63ae56e4e97fb12053590e41a4fa59e7daa74a4</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux-2.6 | ||
Linux Kernel | <2.6.36.1 | |
Fedora | =13 | |
openSUSE | =11.2 | |
openSUSE | =11.3 | |
SUSE Linux Enterprise Desktop with Beagle | =10-sp3 | |
SUSE Linux Enterprise Desktop with Beagle | =11-sp1 | |
SUSE Linux Enterprise Real Time Extension | =11-sp1 | |
SUSE Linux Enterprise Server | =9 | |
SUSE Linux Enterprise Server | =10-sp3 | |
SUSE Linux Enterprise Server | =11-sp1 | |
SUSE Linux Enterprise Software Development Kit | =10-sp3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-4157 is considered a medium severity vulnerability that can lead to denial of service or potential arbitrary code execution.
To fix CVE-2010-4157, you should update your kernel to a version that includes the patch addressing this vulnerability.
CVE-2010-4157 affects multiple Linux kernel versions, particularly those prior to 2.6.36.1, and various distributions, including Debian, Fedora, and openSUSE.
CVE-2010-4157 is a type of integer overflow vulnerability caused by improper handling of size parameters during memory allocation.
There have been no public reports of active exploitation of CVE-2010-4157, but it is recommended to mitigate it due to its potential impact.