CVE-2014-4014 is a flaw in the Linux kernel capabilities implementation affecting versions before 3.14.8. The implementation incorrectly applies user-namespace capability considerations to inode permission checks, despite inodes not being namespaced. A local user can create a user namespace and bypass intended chmod restrictions, including setting the setgid bit on a file whose group is root.
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 (1 hidden).
This repository contains a proof-of-concept (PoC) exploit for CVE-2014-4014, a local privilege escalation vulnerability in the Linux kernel. The repository consists of a single C source file ('cve-2014-4014.c') and a README linking to a blog post with further details. The exploit works by creating a new user namespace and manipulating the UID mapping via '/proc/[pid]/uid_map'. It then sets the setgid bit on a user-specified file, which can be used to escalate privileges. The exploit must be run locally on a vulnerable Linux system, and the user must provide a file path as an argument. The code is concise and demonstrates the vulnerability without weaponization or automation, making it a classic PoC. No network endpoints are present; the only fingerprintable endpoint is the use of the '/proc/[pid]/uid_map' file.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.