USN-1792-1: Linux kernel vulnerabilities
Mathias Krause discovered several errors in the Linux kernel's xfrmuser implementation. A local attacker could exploit these flaws to examine parts of kernel memory. (CVE-2012-6537) Mathias Krause discovered information leak in the Linux kernel's compat ioctl interface. A local user could exploit the flaw to examine parts of kernel stack memory (CVE-2012-6539) Mathias Krause discovered an information leak in the Linux kernel's getsockopt for IPVSSOGETTIMEOUT. A local user could exploit this flaw to examine parts of kernel stack memory. (CVE-2012-6540) Emese Revfy discovered that in the Linux kernel signal handlers could leak address information across an exec, making it possible to by pass ASLR (Address Space Layout Randomization). A local user could use this flaw to by pass ASLR to reliably deliver an exploit payload that would otherwise be stopped (by ASLR). (CVE-2013-0914) A memory use after free error was discover in the Linux kernel's tmpfs filesystem. A local user could exploit this flaw to gain privileges or cause a denial of service (system crash). (CVE-2013-1767) Mateusz Guzik discovered a race in the Linux kernel's keyring. A local user could exploit this flaw to cause a denial of service (system crash). (CVE-2013-1792)
Affected Software
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-1792-1?
USN-1792-1 is considered a high-severity vulnerability due to its potential exploitation by local attackers to access sensitive kernel memory.
How do I fix USN-1792-1?
To address USN-1792-1, upgrade your system to the latest kernel version by installing linux-image-2.6.32-46.107 or later.
Which systems are affected by USN-1792-1?
USN-1792-1 affects Ubuntu 10.04 systems with specific kernel versions from the 2.6.32 series.
What types of attacks can exploit USN-1792-1?
Attackers can exploit USN-1792-1 to perform local information leaks, potentially revealing sensitive data from kernel memory.
Is there a workaround for USN-1792-1?
The best course of action for USN-1792-1 is to apply the security update, as no reliable workaround exists that fully mitigates the risk.