USN-1653-1: Linux kernel (EC2) vulnerability
Rodrigo Freire discovered a flaw in the Linux kernel's TCP illinois congestion control algorithm. A local attacker could use this to cause a denial of service. (CVE-2012-4565) Mathias Krause discovered an information leak in the Linux kernel's TUN/TAP device driver. A local user could exploit this flaw to examine part of the kernel's stack memory. (CVE-2012-6547) Denys Fedoryshchenko discovered a flaw in the Linux kernel's TCP receive processing for IPv4. A remote attacker could exploit this flaw to cause a denial of service (kernel resource consumption) via a flood of SYN+FIN TCP packets. (CVE-2012-6638) A flaw was discovered in the requeuing of futexes in the Linux kernel. A local user could exploit this flaw to cause a denial of service (system crash) or possibly have other unspecified impact. (CVE-2012-6647) A flaw was found in Linux kernel's validation of CIPSO (Common IP Security Option) options set from userspace. A local user that can set a socket's CIPSO options could exploit this flaw to cause a denial of service (crash the system). (CVE-2013-0310) Mathias Krause discover an error in Linux kernel's Datagram Congestion Control Protocol (DCCP) Congestion Control Identifier (CCID) use. A local attack could exploit this flaw to cause a denial of service (crash) and potentially escalate privileges if the user can mmap page 0. (CVE-2013-1827)
Affected Software
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-1653-1?
The severity of USN-1653-1 is categorized as important due to its potential to cause denial of service.
How do I fix USN-1653-1?
You can fix USN-1653-1 by updating your Linux kernel to the latest patched version of 2.6.32-350.57.
Which systems are affected by USN-1653-1?
USN-1653-1 affects Ubuntu 10.04 systems running the linux-image-2.6.32-350-ec2 package.
What vulnerabilities are addressed in USN-1653-1?
USN-1653-1 addresses vulnerabilities related to the TCP illinois congestion control algorithm and an information leak in the TUN/TAP device driver.
Can a remote attacker exploit USN-1653-1?
No, USN-1653-1 can only be exploited by a local attacker due to the nature of the identified vulnerabilities.