The remote Scientific Linux host is missing one or more security
The kernel packages contain the Linux kernel, the core of any Linux
This update fixes the following security issues :
- A flaw was found in the way socket buffers (skb)
requiring TSO (TCP segment offloading) were handled by
the sfc driver. If the skb did not fit within the
minimum-size of the transmission queue, the network card
could repeatedly reset itself. A remote attacker could
use this flaw to cause a denial of service.
- A use-after-free flaw was found in the xacct_add_tsk()
function in the Linux kernel's taskstats subsystem. A
local, unprivileged user could use this flaw to cause an
information leak or a denial of service. (CVE-2012-3510,
- A buffer overflow flaw was found in the hfs_bnode_read()
function in the HFS Plus (HFS+) file system
implementation in the Linux kernel. A local user able to
mount a specially crafted HFS+ file system image could
use this flaw to cause a denial of service or escalate
their privileges. (CVE-2012-2319, Low)
- A flaw was found in the way the msg_namelen variable in
the rds_recvmsg() function of the Linux kernel's
Reliable Datagram Sockets (RDS) protocol implementation
was initialized. A local, unprivileged user could use
this flaw to leak kernel stack memory to user-space.
This update also fixes the following bugs :
- The cpuid_whitelist() function, masking the Enhanced
Intel SpeedStep (EST) flag from all guests, prevented
the 'cpuspeed' service from working in the privileged
Xen domain (dom0). CPU scaling was therefore not
possible. With this update, cpuid_whitelist() is aware
whether the domain executing CPUID is privileged or not,
and enables the EST flag for dom0.
- If a delayed-allocation write was performed before quota
was enabled, the kernel displayed the following warning
WARNING: at fs/quota/dquot.c:988
This was because information about the delayed allocation was not
recorded in the quota structure. With this update, writes prior to
enabling quota are properly accounted for, and the message is not
- Some subsystems clear the TIF_SIGPENDING flag during
error handling in fork() paths. Previously, if the flag
was cleared, the ERESTARTNOINTR error code could be
returned. The underlying source code has been modified
so that the error code is no longer returned.
- An unnecessary check for the RXCW.CW bit could cause the
Intel e1000e NIC (Network Interface Controller) to not
work properly. The check has been removed so that the
Intel e1000e NIC works as expected.
Users should upgrade to these updated packages, which contain
backported patches to correct these issues. The system must be
rebooted for this update to take effect.
See also :
Update the affected packages.
Risk factor :
High / CVSS Base Score : 7.8