CVE-2017-18595: Use After Free

Published Sep 4, 2019
·
Updated

A flaw was found in the allocatetracebuffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer (buf->buffer) still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a dangling pointer issue.

Other sources

An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocatetracebuffer in the file kernel/trace/trace.c.

Affected Software

43 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1127.8.2.rt56.1103.el7
0:3.10.0-1127.8.2.rt56.1103.el7
redhat/kernel<0:3.10.0-1127.8.2.el7
0:3.10.0-1127.8.2.el7
redhat/kernel-alt<0:4.14.0-115.21.2.el7a
0:4.14.0-115.21.2.el7a
redhat/kernel<0:3.10.0-327.88.1.el7
0:3.10.0-327.88.1.el7
redhat/kernel<0:3.10.0-514.76.1.el7
0:3.10.0-514.76.1.el7
redhat/kernel<0:3.10.0-693.67.1.el7
0:3.10.0-693.67.1.el7
redhat/kernel<0:3.10.0-957.54.1.el7
0:3.10.0-957.54.1.el7
redhat/kernel<0:3.10.0-1062.26.1.el7
0:3.10.0-1062.26.1.el7
redhat/kernel-rt<1:3.10.0-693.67.1.rt56.665.el6
1:3.10.0-693.67.1.rt56.665.el6
Linux Linux kernel<4.14.11
openSUSE Leap=15.0
openSUSE Leap=15.1
Linux Linux kernel>=3.10<3.16.55
Linux Linux kernel>=3.17<3.18.91
Linux Linux kernel>=3.19<4.1.50
Linux Linux kernel>=4.2<4.4.109
Linux Linux kernel>=4.5<4.9.74
Linux Linux kernel>=4.10<4.14.11
ubuntu/linux-aws<4.4.0-1016.16
4.4.0-1016.16
ubuntu/linux-lts-xenial<4.4.0-119.143~14.04.1
4.4.0-119.143~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-119.143
4.4.0-119.143
ubuntu/linux-aws<4.4.0-1054.63
4.4.0-1054.63
ubuntu/linux-azure<4.15.0-1013.13~16.04.2
4.15.0-1013.13~16.04.2
ubuntu/linux-gcp<4.15.0-1014.14~16.04.1
4.15.0-1014.14~16.04.1
ubuntu/linux-hwe<4.15.0-24.26~16.04.1
4.15.0-24.26~16.04.1
ubuntu/linux-kvm<4.4.0-1020.25
4.4.0-1020.25
ubuntu/linux-raspi2<4.4.0-1086.94
4.4.0-1086.94
ubuntu/linux-snapdragon<4.4.0-1088.93
4.4.0-1088.93
ubuntu/linux-fips<4.4.0-1008.10
4.4.0-1008.10
ubuntu/linux-snapdragon<4.15.0-1053.57
4.15.0-1053.57
ubuntu/linux-azure-fde*
ubuntu/linux-gke*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-azure-6.11*
ubuntu/linux-gcp-6.11*
ubuntu/linux-hwe-6.11*
ubuntu/linux-lowlatency-hwe-6.11*
ubuntu/linux-raspi-realtime*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:3.10.0-1127.8.2.rt56.1103.el7
  2. Upgrade

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

    Fixed in 0:3.10.0-1127.8.2.el7
  3. Upgrade

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

    Fixed in 0:4.14.0-115.21.2.el7a
  4. Upgrade

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

    Fixed in 0:3.10.0-327.88.1.el7
  5. Upgrade

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

    Fixed in 0:3.10.0-514.76.1.el7
  6. Upgrade

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

    Fixed in 0:3.10.0-693.67.1.el7
  7. Upgrade

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

    Fixed in 0:3.10.0-957.54.1.el7
  8. Upgrade

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

    Fixed in 0:3.10.0-1062.26.1.el7
  9. Upgrade

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

    Fixed in 1:3.10.0-693.67.1.rt56.665.el6
  10. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.4.0-1016.16
  11. Upgrade

    Upgrade ubuntu/linux-lts-xenial to a version that resolves this vulnerability.

    Fixed in 4.4.0-119.143~14.04.1
  12. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 4.4.0-119.143
  13. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.4.0-1054.63
  14. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.15.0-1013.13~16.04.2
  15. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 4.15.0-1014.14~16.04.1
  16. Upgrade

    Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.

    Fixed in 4.15.0-24.26~16.04.1
  17. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 4.4.0-1020.25
  18. Upgrade

    Upgrade ubuntu/linux-raspi2 to a version that resolves this vulnerability.

    Fixed in 4.4.0-1086.94
  19. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.4.0-1088.93
  20. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 4.4.0-1008.10
  21. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.15.0-1053.57
  22. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.14.11

Event History

Sep 4, 2019
CVE Published
12:00 AM
CVE Published
via MITRE·08:33 PM
Data Sourced
via MITRE·08:33 PM
Description
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software
Oct 4, 2019
Data Sourced
via Red Hat·07:50 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2017-18595?

CVE-2017-18595 is classified as a high severity vulnerability due to the potential for a use-after-free condition that could lead to arbitrary code execution.

2

How do I fix CVE-2017-18595?

To fix CVE-2017-18595, update to the appropriate remedied kernel versions specified in the vulnerability details, such as 0:3.10.0-1127.8.2.rt56.1103.el7 or equivalent.

3

Which kernel versions are affected by CVE-2017-18595?

CVE-2017-18595 affects various kernel versions, including several 3.10.x series and some 4.x series kernels up to 4.14.11.

4

What systems are primarily at risk from CVE-2017-18595?

CVE-2017-18595 primarily affects Linux-based systems running vulnerable kernel versions of Red Hat and openSUSE.

5

What are the potential impacts of CVE-2017-18595?

The potential impacts of CVE-2017-18595 include system crashes, arbitrary code execution, and unauthorized access to sensitive data.

Company

Resources

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