RHSA-2017:1491: Important: kernel security and bug fix update

Published Jun 19, 2017
·
Updated

The kernel packages contain the Linux kernel, the core of any Linux operating system.Security Fix(es): A flaw was found in the way memory was being allocated on the stack for user space binaries. If heap (or different memory region) and stack memory regions were adjacent to each other, an attacker could use this flaw to jump over the stack guard gap, cause controlled memory corruption on process stack or the adjacent memory region, and thus increase their privileges on the system. This is a kernel-side mitigation which increases the stack guard gap size from one page to 1 MiB to make successful exploitation of this issue more difficult. (CVE-2017-1000364, Important) Red Hat would like to thank Qualys Research Labs for reporting this issue.Bug Fix(es): Previously, a kernel panic occurred when the mcelog daemon executed a huge page memory offline. This update fixes the HugeTLB feature of the Linux kernel to check for the Page Table Entry (PTE) NULL pointer in the pagecheckaddress() function. As a result, the kernel panic no longer occurs under the described circumstances. (BZ#1444342) Previously, the kdump mechanism was trying to get the lock by the vmallocsyncall() function during a kernel panic. Consequently, a deadlock occurred, and the crashkernel did not boot. This update fixes the vmallocsyncall() function to avoid synchronizing the vmalloc area on the crashing CPU. As a result, the crashkernel parameter now boots as expected, and the kernel dump is collected successfully under the described circumstances. (BZ#1443494)

Affected Software

28 affected componentsFixes available
redhat/kernel<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-debug<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-debug-debuginfo<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-debug-devel<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-debuginfo<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-devel<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-doc<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-firmware<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel-headers<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/perf<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/perf-debuginfo<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/python-perf<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/python-perf-debuginfo<2.6.32-220.72.2.el6
2.6.32-220.72.2.el6
redhat/kernel<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-debug<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-debug-debuginfo<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-debug-devel<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-debuginfo<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-debuginfo-common-x86_64<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-devel<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-doc<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-firmware<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/kernel-headers<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/perf<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/perf-debuginfo<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/python-perf-debuginfo<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6
redhat/python-perf<0:2.6.32-220.72.2.el6
0:2.6.32-220.72.2.el6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  2. Upgrade

    Upgrade redhat/kernel-debug to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  3. Upgrade

    Upgrade redhat/kernel-debug-debuginfo to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  4. Upgrade

    Upgrade redhat/kernel-debug-devel to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  5. Upgrade

    Upgrade redhat/kernel-debuginfo to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  6. Upgrade

    Upgrade redhat/kernel-devel to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  7. Upgrade

    Upgrade redhat/kernel-doc to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  8. Upgrade

    Upgrade redhat/kernel-firmware to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  9. Upgrade

    Upgrade redhat/kernel-headers to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  10. Upgrade

    Upgrade redhat/perf to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  11. Upgrade

    Upgrade redhat/perf-debuginfo to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  12. Upgrade

    Upgrade redhat/python-perf to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  13. Upgrade

    Upgrade redhat/python-perf-debuginfo to a version that resolves this vulnerability.

    Fixed in 2.6.32-220.72.2.el6
  14. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  15. Upgrade

    Upgrade redhat/kernel-debug to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  16. Upgrade

    Upgrade redhat/kernel-debug-debuginfo to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  17. Upgrade

    Upgrade redhat/kernel-debug-devel to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  18. Upgrade

    Upgrade redhat/kernel-debuginfo to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  19. Upgrade

    Upgrade redhat/kernel-debuginfo-common-x86_64 to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  20. Upgrade

    Upgrade redhat/kernel-devel to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  21. Upgrade

    Upgrade redhat/kernel-doc to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  22. Upgrade

    Upgrade redhat/kernel-firmware to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  23. Upgrade

    Upgrade redhat/kernel-headers to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  24. Upgrade

    Upgrade redhat/perf to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  25. Upgrade

    Upgrade redhat/perf-debuginfo to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  26. Upgrade

    Upgrade redhat/python-perf-debuginfo to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  27. Upgrade

    Upgrade redhat/python-perf to a version that resolves this vulnerability.

    Fixed in 0:2.6.32-220.72.2.el6
  28. Compensating control

    Use the kernel-side mitigation that increases the stack guard gap from one page to 1 MiB, making successful exploitation more difficult.

  29. Operational

    Reboot the system for the update to take effect.

Event History

Jun 19, 2017
Advisory Published
via Red Hat·12:00 AM
Sep 13, 2024
Advisory Published
via OSV·02:41 PM
Data Sourced
via OSV·02:41 PM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of RHSA-2017:1491?

The severity of RHSA-2017:1491 is classified as Important.

2

How do I fix RHSA-2017:1491?

To fix RHSA-2017:1491, you should update the kernel packages to version 2.6.32-220.72.2.el6 or later.

3

What systems are affected by RHSA-2017:1491?

RHSA-2017:1491 affects Red Hat Enterprise Linux 6 with specific kernel versions.

4

What is the nature of the vulnerability in RHSA-2017:1491?

The vulnerability in RHSA-2017:1491 involves improper memory allocation on the stack for user space binaries.

5

What are the possible consequences of not addressing RHSA-2017:1491?

Failing to address RHSA-2017:1491 could lead to potential exploit vulnerabilities that may compromise system integrity.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203