Unauthorized device access via failed SELinux cleanup
Published Apr 22, 2026 · Updated Apr 22, 2026
Improper security-label handling in uutils coreutils before 0.6.0 allows local users to access mislabeled device nodes. The mknod path creates a node before applying its SELinux context, then calls std::fs::remove_dir after labeling fails even though that function cannot remove device nodes or FIFOs. Exploitation requires a privileged mknod invocation on an SELinux-enforcing Linux system with a context-setting failure; the leftover node can bypass intended mandatory-access restrictions.
Summary
What happened
Improper security-label handling in uutils coreutils before 0.6.0 allows local users to access mislabeled device nodes. The mknod path creates a node before applying its SELinux context, then calls std::fs::remove_dir after labeling fails even though that function cannot remove device nodes or FIFOs. Exploitation requires a privileged mknod invocation on an SELinux-enforcing Linux system with a context-setting failure; the leftover node can bypass intended mandatory-access restrictions.
The record
- CVE
- CVE-2026-35361
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- uutils
- Product
- coreutils
- Classifications
- CWE-281, CWE-459
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Upstream invalid-context mknod reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo