Differences between revisions 5 and 6
Revision 5 as of 2009-10-23 01:54:28
Size: 2858
Editor: GeoffSimmons
Comment: DebianBug
Revision 6 as of 2009-10-25 21:32:05
Size: 3122
Editor: ?JensWeibler
Comment: A student complained about problems with bitbake
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:
== bitbake ==
From the [[http://docs.openembedded.org/usermanual/html/gettingoe_building_software.html|OpenEmbedded User Manual]]:
''BitBake might complain that there is a problem with the setting in /proc/sys/vm/mmap_min_addr, which needs to be set to zero.''


mmap_min_addr is a kernel tunable that specifies the minimum virtual address that a process is allowed to mmap. Allowing processes to map low values increases the security implications of a class of defects known as "kernel NULL pointer dereference" defects. If a malicious local user finds a way to trigger one of these NULL pointer defects, they can exploit it to cause system hangs, crashes, or otherwise make parts of the system unusable. If this user is also able to map low portions of virtual memory, they can often further exploit this issue to gain increased privileges.

The downside to preventing applications from mmap'ing low virtual memory addresses is that certain applications depend on this functionality. dosemu, qemu and wine are three such applications that exist in Debian 5.0 ('lenny'). See the application specific information below.

Current status

Debian 5.0.3 ships with a default mmap_min_addr of '0'. This means that the Debian system, by default, is susceptible to these NULL-pointer privilege escalation techniques. Unless you know that you have applications that require this functionality, it is recommended that you increase the value of mmap_min_addr on your system.

To do this, you can cut & paste the following commands:

# echo "vm.mmap_min_addr = 32768" > /etc/sysctl.d/mmap_min_addr.conf
# /etc/init.d/procps restart

Future plans

Starting with Debian 5.0.4, the default value of mmap_min_addr will be increased to 4096. If you find this prevents you from running certain applications, you can remove this restriction using the following commands:

# echo "vm.mmap_min_addr = 0" > /etc/sysctl.d/mmap_min_addr.conf
# /etc/init.d/procps restart

If you only need to run the affected application infrequently, you can temporarily decrease the value using the following command:

# sysctl -w vm.mmap_min_addr="0"

You can then reactivate the restriction by running the following command:

# sysctl -w vm.mmap_min_addr="4096"

Application specific information


From the OpenEmbedded User Manual: ?BitBake might complain that there is a problem with the setting in /proc/sys/vm/mmap_min_addr, which needs to be set to zero.


dosemu must run with vm.mmap_min_addr set to 0, or be executed as root. The maintainers are investigating ways of dealing with this issue in packaging, see: 505247


Only Win16 binaries require the ability to mmap low addresses, Win32 binaries do not. It is recommended that you test your application with the increase mmap_min_addr setting. If the application starts up without issue, then you should not need to remove the mmap_min_addr restriction.


qemu, as shipped in Debian 5.0, requires low virtual memory mmaps. mmap_min_addr must be set to 0 to run qemu as a non-root user. This limitation has been removed upstream, so qemu should work with an increase mmap_min_addr starting with Debian squeeze.