Loading vulnerability…
CVE-2026-35361 is a local security flaw in the uutils coreutils implementation of mknod. The utility creates a device node or FIFO before SELinux labeling is successfully applied, so security labeling is not handled atomically. If SELinux context application fails, the vulnerable code path in src/uu/mknod/src/mknod.rs attempts cleanup with std::fs::remove_dir(file_name). Because the created object is a special file rather than a directory, remove_dir fails with ENOTDIR and the cleanup failure is silently ignored. As a result, the node can remain on disk with the parent directory's inherited default SELinux context instead of the intended restrictive label. The content also describes a race window between node creation and context application, allowing a local attacker to open the node before the intended SELinux context is set. The referenced fix replaces std::fs::remove_dir with std::fs::remove_file so orphaned special files are correctly deleted when labeling fails.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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, 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.