USN-1256-1: Linux kernel (Natty backport) vulnerabilities

Ubuntu Security Notice USN-1256-1

linux-lts-backport-natty vulnerabilities

A security issue affects these releases of Ubuntu and its
derivatives:

Ubuntu 10.04 LTS

Summary

Several security issues were fixed in the kernel.

Software description

linux-lts-backport-natty
- Linux kernel backport from Natty

Details

It was discovered that the /proc filesystem did not correctly handlepermission changes when programs executed. A local attacker could hold openfiles to examine details about programs running with higher privileges,potentially increasing the chances of exploiting additionalvulnerabilities. (CVE-2011-1020)

Vasiliy Kulikov discovered that the Bluetooth stack did not correctly clearmemory. A local attacker could exploit this to read kernel stack memory,leading to a loss of privacy. (CVE-2011-1078)

Vasiliy Kulikov discovered that the Bluetooth stack did not correctly checkthat device name strings were NULL terminated. A local attacker couldexploit this to crash the system, leading to a denial of service, or leakcontents of kernel stack memory, leading to a loss of privacy.(CVE-2011-1079)

Vasiliy Kulikov discovered that bridge network filtering did not check thatname fields were NULL terminated. A local attacker could exploit this toleak contents of kernel stack memory, leading to a loss of privacy.(CVE-2011-1080)

Johan Hovold discovered that the DCCP network stack did not correctlyhandle certain packet combinations. A remote attacker could send speciallycrafted network traffic that would crash the system, leading to a denial ofservice. (CVE-2011-1093)

Peter Huewe discovered that the TPM device did not correctly initializememory. A local attacker could exploit this to read kernel heap memorycontents, leading to a loss of privacy. (CVE-2011-1160)

Dan Rosenberg discovered that the IRDA subsystem did not correctly checkcertain field sizes. If a system was using IRDA, a remote attacker couldsend specially crafted traffic to crash the system or gain root privileges.(CVE-2011-1180)

Ryan Sweat discovered that the GRO code did not correctly validate memory.In some configurations on systems using VLANs, a remote attacker could sendspecially crafted traffic to crash the system, leading to a denial ofservice. (CVE-2011-1478)

It was discovered that the security fix for CVE-2010-4250 introduced aregression. A remote attacker could exploit this to crash the system,leading to a denial of service. (CVE-2011-1479)

Dan Rosenberg discovered that the X.25 Rose network stack did not correctlyhandle certain fields. If a system was running with Rose enabled, a remoteattacker could send specially crafted traffic to gain root privileges.(CVE-2011-1493)

It was discovered that the Stream Control Transmission Protocol (SCTP)implementation incorrectly calculated lengths. If the net.sctp.addip_enablevariable was turned on, a remote attacker could send specially craftedtraffic to crash the system. (CVE-2011-1573)

Ryan Sweat discovered that the kernel incorrectly handled certain VLANpackets. On some systems, a remote attacker could send specially craftedtraffic to crash the system, leading to a denial of service.(CVE-2011-1576)

Timo Warns discovered that the GUID partition parsing routines did notcorrectly validate certain structures. A local attacker with physicalaccess could plug in a specially crafted block device to crash the system,leading to a denial of service. (CVE-2011-1577)

Phil Oester discovered that the network bonding system did not correctlyhandle large queues. On some systems, a remote attacker could sendspecially crafted traffic to crash the system, leading to a denial ofservice. (CVE-2011-1581)

It was discovered that CIFS incorrectly handled authentication. When a userhad a CIFS share mounted that required authentication, a local user couldmount the same share without knowing the correct password. (CVE-2011-1585)

It was discovered that the GRE protocol incorrectly handled netnsinitialization. A remote attacker could send a packet while the ip_gremodule was loading, and crash the system, leading to a denial of service.(CVE-2011-1767)

It was discovered that the IP/IP protocol incorrectly handled netnsinitialization. A remote attacker could send a packet while the ipip modulewas loading, and crash the system, leading to a denial of service.(CVE-2011-1768)

Ben Greear discovered that CIFS did not correctly handle direct I/O. Alocal attacker with access to a CIFS partition could exploit this to crashthe system, leading to a denial of service. (CVE-2011-1771)

Timo Warns discovered that the EFI GUID partition table was not correctlyparsed. A physically local attacker that could insert mountable devicescould exploit this to crash the system or possibly gain root privileges.(CVE-2011-1776)

Vasiliy Kulikov and Dan Rosenberg discovered that ecryptfs did notcorrectly check the origin of mount points. A local attacker could exploitthis to trick the system into unmounting arbitrary mount points, leading toa denial of service. (CVE-2011-1833)

Ben Hutchings reported a flaw in the kernel's handling of corrupt LDMpartitions. A local user could exploit this to cause a denial of service orescalate privileges. (CVE-2011-2182)

Dan Rosenberg discovered that the IPv4 diagnostic routines did notcorrectly validate certain requests. A local attacker could exploit this toconsume CPU resources, leading to a denial of service. (CVE-2011-2213)

It was discovered that an mmap() call with the MAP_PRIVATE flag on"/dev/zero" was incorrectly handled. A local attacker could exploit this tocrash the system, leading to a denial of service. (CVE-2011-2479)

Vasiliy Kulikov discovered that taskstats listeners were not correctlyhandled. A local attacker could expoit this to exhaust memory and CPUresources, leading to a denial of service. (CVE-2011-2484)

It was discovered that Bluetooth l2cap and rfcomm did not correctlyinitialize structures. A local attacker could exploit this to read portionsof the kernel stack, leading to a loss of privacy. (CVE-2011-2492)

Sami Liedes discovered that ext4 did not correctly handle missing rootinodes. A local attacker could trigger the mount of a specially craftedfilesystem to cause the system to crash, leading to a denial of service.(CVE-2011-2493)

Robert Swiecki discovered that mapping extensions were incorrectly handled.A local attacker could exploit this to crash the system, leading to adenial of service. (CVE-2011-2496)

Dan Rosenberg discovered that the Bluetooth stack incorrectly handledcertain L2CAP requests. If a system was using Bluetooth, a remote attackercould send specially crafted traffic to crash the system or gain rootprivileges. (CVE-2011-2497)

Ben Pfaff discovered that Classless Queuing Disciplines (qdiscs) were beingincorrectly handled. A local attacker could exploit this to crash thesystem, leading to a denial of service. (CVE-2011-2525)

It was discovered that GFS2 did not correctly check block sizes. A localattacker could exploit this to crash the system, leading to a denial ofservice. (CVE-2011-2689)

It was discovered that the EXT4 filesystem contained multiple off-by-oneflaws. A local attacker could exploit this to crash the system, leading toa denial of service. (CVE-2011-2695)

Fernando Gont discovered that the IPv6 stack used predictable fragmentidentification numbers. A remote attacker could exploit this to exhaustnetwork resources, leading to a denial of service. (CVE-2011-2699)

Mauro Carvalho Chehab discovered that the si4713 radio driver did notcorrectly check the length of memory copies. If this hardware wasavailable, a local attacker could exploit this to crash the system or gainroot privileges. (CVE-2011-2700)

The performance counter subsystem did not correctly handle certaincounters. A local attacker could exploit this to crash the system, leadingto a denial of service. (CVE-2011-2918)

Time Warns discovered that long symlinks were incorrectly handled on Befilesystems. A local attacker could exploit this with a malformed Befilesystem and crash the system, leading to a denial of service.(CVE-2011-2928)

Qianfeng Zhang discovered that the bridge networking interface incorrectlyhandled certain network packets. A remote attacker could exploit this tocrash the system, leading to a denial of service. (CVE-2011-2942)

Dan Kaminsky discovered that the kernel incorrectly handled random sequencenumber generation. An attacker could use this flaw to possibly predictsequence numbers and inject packets. (CVE-2011-3188)

Darren Lavender discovered that the CIFS client incorrectly handled certainlarge values. A remote attacker with a malicious server could exploit thisto crash the system or possibly execute arbitrary code as the root user.(CVE-2011-3191)

Yasuaki Ishimatsu discovered a flaw in the kernel's clock implementation. Alocal unprivileged attacker could exploit this causing a denial of service.(CVE-2011-3209)

Yogesh Sharma discovered that CIFS did not correctly handle UNCs that hadno prefixpaths. A local attacker with access to a CIFS partition couldexploit this to crash the system, leading to a denial of service.(CVE-2011-3363)

A flaw was discovered in the Linux kernel's AppArmor security interfacewhen invalid information was written to it. An unprivileged local usercould use this to cause a denial of service on the system. (CVE-2011-3619)

A flaw was found in the Linux kernel's /proc/*/*map* interface. A local,unprivileged user could exploit this flaw to cause a denial of service.(CVE-2011-3637)

Scot Doyle discovered that the bridge networking interface incorrectlyhandled certain network packets. A remote attacker could exploit this tocrash the system, leading to a denial of service. (CVE-2011-4087)

A bug was found in the way headroom check was performed inudp6_ufo_fragment() function. A remote attacker could use this flaw tocrash the system. (CVE-2011-4326)

Ben Hutchings discovered several flaws in the Linux Rose (X.25 PLP) layer.A local user or a remote user on an X.25 network could exploit these flawsto execute arbitrary code as root. (CVE-2011-4914)

Update instructions

The problem can be corrected by updating your system to the following
package version:

After a standard system update you need to reboot your computer to makeall the necessary changes.

ATTENTION: Due to an unavoidable ABI change the kernel updates havebeen given a new version number, which requires you to recompile andreinstall all third party kernel modules you might have installed. Ifyou use linux-restricted-modules, you have to update that package aswell to get modules which work with the new kernel version. Unless youmanually uninstalled the standard kernel metapackages (e.g. linux-generic,linux-server, linux-powerpc), a standard system upgrade will automaticallyperform this as well.