runc procfs write redirection and LSM bypass
CVE-2025-52881 is a race-condition vulnerability in runc, the OCI container runtime, that allows an attacker to trick runc into redirecting writes intended for procfs files to unintended procfs targets. The issue affects runc 1.2.7, 1.3.2, and 1.4.0-rc.2, and broader reporting describes it as affecting all known versions prior to the fixed releases. Exploitation relies on a racing container with shared mounts so that, during runc's handling of writes to /proc, the attacker can cause path resolution to be redirected via symlinks in tmpfs or potentially bind mounts. The flaw is particularly relevant to writes associated with Linux Security Module relabeling and sysctl handling. The vulnerability is described as a more sophisticated variant of CVE-2019-19921 because the earlier mitigation only verified that certain LSM-label writes targeted procfs, which was insufficient to prevent redirected-write abuse. Successful exploitation can transform ordinary runc writes into attacker-controlled writes to sensitive procfs files such as /proc/sysrq-trigger or /proc/sys/kernel/core_pattern.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Affected products & vendors
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.
Recent activity
53 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in runc allows attackers to bypass SELinux and AppArmor protections by redirecting writes to procfs files, enabling full host compromise from a container.
A vulnerability in runC that allows circumvention of Linux Security Module (LSM) relabel protections, enabling arbitrary writes and facilitating container escape.
A vulnerability in runC allowing attackers to redirect writes to /proc, bypassing LSM relabel protections and enabling arbitrary writes to sensitive files, potentially leading to container escape.
High-severity runc issue enabling arbitrary write redirection within /proc via mount-namespace and symlink manipulation, potentially bypassing LSM controls (AppArmor/SELinux) and enabling host crash or host root code execution (e.g., via /proc/sysrq-trigger or /proc/sys/kernel/core_pattern).
The version that knows your environment.
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.