Linux kernel do_mremap() local privilege escalation vulnerability — GLSA 200401-01

A critical security vulnerability has been found in recent Linux kernels which allows for local privelege escalation.

Affected packages

Background

The Linux kernel is responsible for memory management in a working system - to allow this, processes are allowed to allocate and unallocate memory.

Description

The memory subsystem allows 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 privileges 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.

Resolution

 $> 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.

References

• Vulnerability

Release date
January 08, 2004

Latest revision
January 08, 2004: 01

Severity
high

Exploitable
local

Bugzilla entries

• 37292