CVE-2017-6074: Double Free

Published Feb 17, 2017
·
Updated

A flaw was found in the linux kernels implementation of DCCP protocol in which a local user could create influence timing in which a skbuff could be used after it had been freed by the kernel. An attacker is able to craft structures allocated in this free memory will be able to create memory corruption, privilege escalation or crash the system. An attacker must have a local account access on the system, this is not a remote attack. An attack requires IPV6 support to be enabled in the system.

Initial message:

https://groups.google.com/forum/#!topic/syzkaller/vGUxJLcdKY

Proposed patch:

https://patchwork.ozlabs.org/patch/728808/

Other sources

A use-after-free flaw was found in the way the Linux kernel's Datagram Congestion Control Protocol (DCCP) implementation freed SKB (socket buffer) resources for a DCCPPKTREQUEST packet when the IPV6RECVPKTINFO option is set on the socket. A local, unprivileged user could use this flaw to alter the kernel memory, allowing them to escalate their privileges on the system.

The dccprcvstateprocess function in net/dccp/input.c in the Linux kernel through 4.9.11 mishandles DCCPPKTREQUEST packet data structures in the LISTEN state, which allows local users to obtain root privileges or cause a denial of service (double free) via an application that makes an IPV6RECVPKTINFO setsockopt system call.

Affected Software

27 affected componentsFixes available
redhat/kernel<0:2.6.18-419.el5
0:2.6.18-419.el5
redhat/kernel<0:2.6.18-238.58.1.el5
0:2.6.18-238.58.1.el5
redhat/kernel<0:2.6.18-348.33.1.el5
0:2.6.18-348.33.1.el5
redhat/kernel<0:2.6.32-642.13.2.el6
0:2.6.32-642.13.2.el6
redhat/kernel<0:2.6.32-220.70.1.el6
0:2.6.32-220.70.1.el6
redhat/kernel<0:2.6.32-358.77.1.el6
0:2.6.32-358.77.1.el6
redhat/kernel<0:2.6.32-431.78.1.el6
0:2.6.32-431.78.1.el6
redhat/kernel<0:2.6.32-504.57.1.el6
0:2.6.32-504.57.1.el6
redhat/kernel<0:2.6.32-573.40.1.el6
0:2.6.32-573.40.1.el6
redhat/kernel-rt<0:3.10.0-514.6.1.rt56.430.el7
0:3.10.0-514.6.1.rt56.430.el7
redhat/kernel<0:3.10.0-514.6.2.el7
0:3.10.0-514.6.2.el7
redhat/kernel<0:3.10.0-229.49.1.ael7b
0:3.10.0-229.49.1.ael7b
redhat/kernel<0:3.10.0-327.49.2.el7
0:3.10.0-327.49.2.el7
redhat/kernel-rt<1:3.10.0-514.rt56.219.el6
1:3.10.0-514.rt56.219.el6
redhat/rhev-hypervisor7<0:7.3-20170425.0.el6e
0:7.3-20170425.0.el6e
redhat/rhev-hypervisor7<0:7.3-20170425.0.el7e
0:7.3-20170425.0.el7e
Google Android
Linux Linux Kernel<3.2.86
Linux Linux Kernel>=3.3<3.10.106
Linux Linux Kernel>=3.11<3.12.71
Linux Linux Kernel>=3.13<3.16.41
Linux Linux Kernel>=3.17<3.18.49
Linux Linux Kernel>=3.19<4.1.41
Linux Linux Kernel>=4.2<4.4.52
Linux Linux Kernel>=4.5<4.9.13
Debian Linux=8.0
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:2.6.18-419.el5
  2. Upgrade

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

    Fixed in 0:2.6.18-238.58.1.el5
  3. Upgrade

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

    Fixed in 0:2.6.18-348.33.1.el5
  4. Upgrade

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

    Fixed in 0:2.6.32-642.13.2.el6
  5. Upgrade

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

    Fixed in 0:2.6.32-220.70.1.el6
  6. Upgrade

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

    Fixed in 0:2.6.32-358.77.1.el6
  7. Upgrade

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

    Fixed in 0:2.6.32-431.78.1.el6
  8. Upgrade

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

    Fixed in 0:2.6.32-504.57.1.el6
  9. Upgrade

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

    Fixed in 0:2.6.32-573.40.1.el6
  10. Upgrade

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

    Fixed in 0:3.10.0-514.6.1.rt56.430.el7
  11. Upgrade

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

    Fixed in 0:3.10.0-514.6.2.el7
  12. Upgrade

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

    Fixed in 0:3.10.0-229.49.1.ael7b
  13. Upgrade

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

    Fixed in 0:3.10.0-327.49.2.el7
  14. Upgrade

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

    Fixed in 1:3.10.0-514.rt56.219.el6
  15. Upgrade

    Upgrade redhat/rhev-hypervisor7 to a version that resolves this vulnerability.

    Fixed in 0:7.3-20170425.0.el6e
  16. Upgrade

    Upgrade redhat/rhev-hypervisor7 to a version that resolves this vulnerability.

    Fixed in 0:7.3-20170425.0.el7e
  17. Upgrade

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

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1
  18. Configuration

    Add to /etc/modprobe.d/blacklist-dccp.conf: alias net-pf-10-proto-0-type-6 off

    Linux kernel module (DCCP) autoloading via modprobe modprobe alias net-pf-10-proto-0-type-6 = off
  19. Configuration

    Add to /etc/modprobe.d/blacklist-dccp.conf: alias net-pf-10-proto-33-type-6 off

    Linux kernel module (DCCP) autoloading via modprobe modprobe alias net-pf-10-proto-33-type-6 = off
  20. Configuration

    Add to /etc/modprobe.d/blacklist-dccp.conf: alias net-pf-2-proto-0-type-6 off

    Linux kernel module (DCCP) autoloading via modprobe modprobe alias net-pf-2-proto-0-type-6 = off
  21. Configuration

    Add to /etc/modprobe.d/blacklist-dccp.conf: alias net-pf-2-proto-33-type-6 off

    Linux kernel module (DCCP) autoloading via modprobe modprobe alias net-pf-2-proto-33-type-6 = off
  22. Operational

    Restart the system if the DCCP modules are already loaded (DCCP kernel modules will be unable to be unloaded while any network interfaces are active and the protocol is in use).

Event History

Feb 17, 2017
Data Sourced
via Red Hat·01:44 AM
DescriptionSeverityAffected Software
Feb 18, 2017
CVE Published
via MITRE·09:40 PM
Data Sourced
via MITRE·09:40 PM
Description
Data Sourced
via NVD·09:59 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·10:38 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:47 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-6074?

CVE-2017-6074 has been classified as a high severity vulnerability due to potential local privilege escalation.

2

How do I fix CVE-2017-6074?

To remediate CVE-2017-6074, upgrade your kernel to a version that is not affected, such as the patched versions provided by Red Hat or Debian.

3

What versions are affected by CVE-2017-6074?

CVE-2017-6074 affects various kernel versions, including older releases of Red Hat and Debian kernels prior to the security patches.

4

Who can be impacted by CVE-2017-6074?

Any local user on affected systems can exploit CVE-2017-6074 to perform actions that may lead to privilege escalation.

5

Is CVE-2017-6074 specific to certain distributions?

Yes, CVE-2017-6074 primarily affects certain versions of the Red Hat kernel and Linux distributions that utilize vulnerable kernel versions.

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