First published: Fri Jul 15 2011(Updated: )
If an extent exists which includes the block right before the maximum file offset, and the block for the maximum file offset is written, the kernel panics. For 4KB block size, the problem only occurs on x86_64 architecture. For 1KB or 2KB block size, the problem occurs on both i386 and x86_64. Local unprivileged users can use this flaw to crash the system when ext4 filesystem is in use. Upstream fix: <a href="http://git.kernel.org/linus/f17722f917b2f21497deb6edc62fb1683daa08e6">http://git.kernel.org/linus/f17722f917b2f21497deb6edc62fb1683daa08e6</a> References: <a href="http://www.spinics.net/lists/linux-ext4/msg25697.html">http://www.spinics.net/lists/linux-ext4/msg25697.html</a>
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Linux kernel | =3.0-rc2 | |
Linux Linux kernel | =3.0-rc4 | |
Linux Linux kernel | =3.0-rc3 | |
Linux Linux kernel | =3.0-rc1 | |
Linux Linux kernel | <3.0 | |
Linux Linux kernel | =3.0 | |
debian/linux-2.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.