|
Vulnerability Assessment & Network Security Forums |
|||||||||
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery. Home >> Browse Vulnerability Assessment Database >> Gentoo Local Security Checks >> [GLSA-200401-01] Linux kernel do_mremap() local privilege escalation vulnerability Vulnerability Assessment Details
|
[GLSA-200401-01] Linux kernel do_mremap() local privilege escalation vulnerability |
||
Linux kernel do_mremap() local privilege escalation vulnerability Detailed Explanation for this Vulnerability Assessment The remote host is affected by the vulnerability described in GLSA-200401-01 (Linux kernel do_mremap() local privilege escalation vulnerability) The memory subsystem permits for shrinking, growing, and moving of chunks of memory along any of the allocated memory areas which the kernel posesses. A typical virtual memory area covers at least one memory page. An incorrect bound check discovered inside the do_mremap() kernel code performing remapping of a virtual memory area may lead to creation of a virtual memory area of 0 bytes length. The problem is based on the general mremap flaw that remapping 2 pages from inside a VMA creates a memory hole of only one page in length but an additional VMA of two pages. In the case of a zero sized remapping request no VMA hole is created but an additional VMA descriptor of 0 bytes in length is created. This advisory also addresses an information leak in the Linux RTC system. Impact Arbitrary code may be able to exploit this vulnerability and may disrupt the operation of other parts of the kernel memory management subroutines finally leading to unexpected behavior. Since no special rights are required to use the mremap(2) system call any process may misuse its unexpected behavior to disrupt the kernel memory management subsystem. Proper exploitation of this vulnerability may lead to local privilege escalation including execution of arbitrary code with kernel level access. Proof-of-concept exploit code has been created and successfully tested, permitting root escalation on vulnerable systems. As a result, all users should upgrade their kernels to new or patched versions. Workaround There is no temporary workaround - a kernel upgrade is required. A list of unaffected kernels is provided along with this announcement. References: http://isec.pl/vulnerabilities/isec-0012-mremap.txt Solution: Users are encouraged to upgrade to the latest available sources for their system: $> emerge sync $> emerge -pv your-favourite-sources $> emerge your-favourite-sources $> # Follow usual procedure for compiling and installing a kernel. $> # If you use genkernel, run genkernel as you would do normally. $> # IF YOUR KERNEL IS MARKED as "remerge required!" THEN $> # YOU SHOULD UPDATE YOUR KERNEL EVEN IF PORTAGE $> # REPORTS THAT THE SAME VERSION IS INSTALLED. Network Security Threat Level: High Networks Security ID: Vulnerability Assessment Copyright: (C) 2005 Michel Arboi |
||
Cables, Connectors |
A-Tech 8GB DDR3 1600 PC3-12800 Laptop SODIMM 204-Pin Memory RAM PC3L DDR3L 1x 8G
$13.99
HyperX FURY DDR3 8GB 16GB 32GB 1600 MHz PC3-12800 Desktop RAM Memory DIMM 240pin
$12.90
A-Tech 8GB PC3-12800 Desktop DDR3 1600 MHz Non ECC 240-Pin DIMM Memory RAM 1x 8G
$13.99
A-Tech 16GB 2 x 8GB PC3-12800 Laptop SODIMM DDR3 1600 Memory RAM PC3L 16G DDR3L
$27.98
8GB PC3L-12800S 1600MHz SODIMM DDR3 RAM | Grade A
$12.00
Kingston HyperX FURY DDR3 8GB 16GB 32G 1600 1866 1333 Desktop Memory RAM DIMM
$13.25
Samsung 16GB (2x8GB) PC3L-12800S Lap Top Memory RAM
$20.00
Team T-FORCE VULCAN Z 16GB (2 x 8GB) 288-Pin PC RAM DDR4 3200 (PC4 25600) XMP
$35.99
A-Tech 256GB 4x 64GB 4Rx4 PC4-19200 ECC Load Reduced LRDIMM Server Memory RAM
$287.96
A-Tech 256GB 8x 32GB 4Rx4 PC4-17000L DDR4 2133 MHz ECC LRDIMM Server Memory RAM
$319.92
|
||
No Discussions have been posted on this vulnerability. |