RHSA-2017:2797

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1

By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1