# CVE-2017-6074: Use after free in n/a > Local attackers can gain root privileges or cause a denial of service via a double free vulnerability in the Linux kernel DCCP implementation. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Feb 2017 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2017-6074, GHSA-2gwg-mmmc-55j4, RHSA-2017:0293, RHSA-2017:0294, RHSA-2017:0295, RHSA-2017:0316, RHSA-2017:0324, RHSA-2017:0345, RHSA-2017:0365, RHSA-2017:0366, RHSA-2017:0403, RHSA-2017:0501, RHSA-2017:1209, UBUNTU-CVE-2017-6074 ## What is CVE-2017-6074? CVE-2017-6074 is a high-severity use after free vulnerability in Debian Debian Linux, published on 18 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description The dccp_rcv_state_process function in net/dccp/input.c in the Linux kernel through 4.9.11 mishandles DCCP_PKT_REQUEST 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 IPV6_RECVPKTINFO setsockopt system call. Weakness: CWE-415 (Double Free) ## Which versions are affected by CVE-2017-6074? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-headers` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `python-perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-642.13.2.el6 | | `kernel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-headers` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `python-perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-642.13.2.el6 | | `rhev-hypervisor7` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:7.3-20170425.0.el6ev | | `kernel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-bootwrapper` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-642.13.2.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-642.13.2.el6 | Products: Debian Debian Linux, Linux kernel. ## How do I fix CVE-2017-6074? Apply the vendor's patch. ## Is CVE-2017-6074 being exploited? There is no known exploitation of CVE-2017-6074 in the wild and no public exploit code. Public exploit code: - https://github.com/BimsaraMalinda/Linux-Kernel-4.4.0-Ubuntu---DCCP-Double-Free-Privilege-Escalation-CVE-2017-6074 (github_poc): https://github.com/BimsaraMalinda/Linux-Kernel-4.4.0-Ubuntu---DCCP-Double-Free-Privilege-Escalation-CVE-2017-6074 - Linux Kernel 4.4.0 (Ubuntu) - DCCP Double-Free (PoC) (exploitdb) - Linux Kernel 4.4.0 (Ubuntu) - DCCP Double-Free Privilege Escalation (exploitdb) - This repository provides a modified version of the original CVE-2017-6074 exploit (use-after-free in the Linux kernel DCCP subsystem), designed only to demonstrate Denial of Service (DoS) impact. An authenticated local user can trigger a kernel panic, causing a total loss of system availability. (github_poc): https://github.com/34zY/CVE-2017-6074-DOS ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-6074 and fix it if it is affected. What it is: CVE-2017-6074 is a high-severity use after free vulnerability in Debian Debian Linux, published on 18 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-6074 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-6074/ (Markdown: https://insights.sbomify.com/CVE-2017-6074/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6074 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6074 - OSV: https://osv.dev/vulnerability/CVE-2017-6074 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-6074/ Summaries are generated and may contain mistakes; the official description above is the record.