RHSA-2010:0380: Important: kernel security and bug fix update

The kernel packages contain the Linux kernel, the core of any Linuxoperating system.Security fixes: a race condition was found in the mac80211 implementation, a framework used for writing drivers for wireless devices. An attacker could triggerthis flaw by sending a Delete Block ACK (DELBA) packet to a target system,resulting in a remote denial of service. Note: This issue only affectedusers on 802.11n networks, and that also use the iwlagn driver with Intelwireless hardware. (CVE-2009-4027, Important) a use-after-free flaw was found in the tcprcvstateprocess() function in the Linux kernel TCP/IP protocol suite implementation. If a system usingIPv6 had the IPV6RECVPKTINFO option set on a listening socket, a remoteattacker could send an IPv6 packet to that system, causing a kernel panic(denial of service). (CVE-2010-1188, Important) a flaw was found in the gfs2lock() implementation. The GFS2 locking code could skip the lock operation for files that have the SISGID bit(set-group-ID on execution) in their mode set. A local, unprivileged useron a system that has a GFS2 file system mounted could use this flaw tocause a kernel panic (denial of service). (CVE-2010-0727, Moderate) a divide-by-zero flaw was found in the ext4 file system code. A local attacker could use this flaw to cause a denial of service by mounting aspecially-crafted ext4 file system. (CVE-2009-4307, Low)Bug fixes: if a program that calls posixfadvise() were compiled on x86, and then run on a 64-bit system, that program could experience various problems,including performance issues and the call to posixfadvise() failing,causing the program to not run as expected or even abort. With this update,when such programs attempt to call posixfadvise() on 64-bit systems,sys32fadvise64() is called instead, which resolves this issue. This updatealso fixes other 32-bit system calls that were mistakenly called on 64-bitsystems (including systems running the kernel-xen kernel). (BZ#569597) on some systems able to set a P-State limit via the BIOS, it was not possible to set the limit to a higher frequency if the system was rebootedwhile a low limit was set:"/sys/devices/system/cpu/cpu[x]/cpufreq/scalingmaxfreq" would retain thelow limit in these situations. With this update, limits are correctly set,even after being changed after a system reboot. (BZ#569727) certain Intel ICH hardware (using the e1000e driver) has an NFS filtering capability that did not work as expected, causing memory corruption, whichcould lead to kernel panics, or other unexpected behavior. In a reportedcase, a panic occurred when running NFS connection tests. This updateresolves this issue by disabling the filtering capability. (BZ#569797) if "open(/proc/[PID]/[xxxx])" was called at the same time the process was exiting, the call would fail with an EINVAL error (an incorrect error forthis situation). With this update, the correct error, ENOENT, is returnedin this situation. (BZ#571362) multiqueue is used for transmitting data, but a single queue transmit ON/OFF scheme was used. This led to a race condition on systems with thebnx2x driver in situations where one queue became full, but not stopped,and the other queue enabled transmission. With this update, only a singlequeue is used. (BZ#576951) the "/proc/sys/vm/mmapminaddr" tunable helps prevent unprivileged users from creating new memory mappings below the minimum address. Thesysctl value for mmapminaddr could be changed by a process or user thathas an effective user ID (euid) of 0, even if the process or user does nothave the CAPSYSRAWIO capability. This update adds a capability check forthe CAPSYSRAWIO capability before allowing the mmapminaddr value to bechanged. (BZ#577206)Users should upgrade to these updated packages, which contain backportedpatches to correct these issues. The system must be rebooted for thisupdate to take effect.