StackRot (CVE-2023-3269) is a use-after-free vulnerability in the Linux kernel memory-management subsystem. Incorrect lock handling while accessing and updating virtual memory areas (VMAs) can leave freed memory reachable, enabling exploitation in kernel context.
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.
This repository contains a full proof-of-concept (PoC) local privilege escalation exploit for the Linux kernel vulnerability CVE-2023-3269 (StackRot), which affects kernel versions 6.1 through 6.4. The exploit targets a use-after-free (UAF) condition in the maple tree VMA management subsystem, allowing an unprivileged local user to escalate privileges to root and escape containers. The repository is well-structured, with the main exploit logic implemented in C under the `exp/src/` directory. The exploit is built as a static binary using a custom minimal C library (`nolibc`) for portability and minimal dependencies. The exploit orchestrates multiple processes and kernel objects (such as message queues and memory mappings) to trigger the UAF, leak kernel addresses, and construct a ROP chain for privilege escalation. The exploit is designed to be run in a QEMU virtual machine with a specific kernel image and configuration, as provided in the `env/` directory. Shell scripts (`exploit.sh`, `as_root.sh`) demonstrate post-exploitation actions, such as reading the root flag. The Makefile automates building and running the exploit in the test environment. Key fingerprintable endpoints include `/proc/self/maps` (used for kernel memory manipulation), `/tmp` (used for deep directory/file creation), and the root flag file (`/root/flag`). The attack vector is strictly local, requiring the attacker to execute code on the target system. The exploit is a PoC and not weaponized, but demonstrates a reliable method for exploiting this class of kernel vulnerabilities.
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.
2 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.