Loading vulnerability…
A double free vulnerability exists in the dccp_rcv_state_process function in net/dccp/input.c in the Linux kernel through version 4.9.11. The flaw is triggered when handling DCCP_PKT_REQUEST packet data structures in the LISTEN state, specifically when an application invokes the IPV6_RECVPKTINFO setsockopt system call. This can result in memory corruption due to the double free of a socket buffer.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single C proof-of-concept exploit (cve-2017-6074-dos-only_Version2.c) and a README.md. The exploit targets CVE-2017-6074, a use-after-free vulnerability in the Linux kernel's DCCP subsystem. The code is designed to demonstrate only a Denial of Service (DoS) impact by triggering a kernel panic when the process is killed after arming the vulnerability. It does not attempt privilege escalation or provide shell access. The exploit requires local user access and is intended for research and testing on authorized systems only. The code sets up a user and network namespace sandbox, manipulates DCCP sockets to trigger the vulnerability, and uses several /proc files and the ifconfig binary for sandbox setup. The README provides clear warnings about the DoS effect and references the CVE and relevant CWE. The exploit is a functional PoC for causing a kernel panic on vulnerable Linux systems.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.