CVE-2026-35361: CWE-281: Improper Preservation of Permissions in Uutils coreutils
The mknod utility in uutils coreutils fails to handle security labels atomically by creating device nodes before setting the SELinux context. If labeling fails, the utility attempts cleanup using std::fs::remove_dir, which cannot remove device nodes or FIFOs. This leaves mislabeled nodes behind with incorrect default contexts, potentially allowing unauthorized access to device nodes that should have been restricted by mandatory access controls.
AI Analysis
Technical Summary
The vulnerability arises because the mknod utility in uutils coreutils does not atomically handle security labels when creating device nodes. Specifically, device nodes are created before the SELinux context is applied. If the labeling fails, the utility tries to clean up using std::fs::remove_dir, which cannot remove device nodes or FIFOs, resulting in leftover nodes with incorrect default security contexts. This improper preservation of permissions (CWE-281) can lead to unauthorized access to device nodes that should be restricted by SELinux mandatory access controls.
Potential Impact
The impact is limited to potential unauthorized access to device nodes due to incorrect SELinux labeling. The CVSS score of 3.4 (low severity) reflects limited confidentiality and integrity impact, requiring local privileges with high complexity and no user interaction. There is no indication of availability impact or known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — no official fix or patch links are provided. Users should monitor the vendor advisory for updates. Until a fix is available, cautious use of the mknod utility in uutils coreutils is advised, especially in environments relying on SELinux for mandatory access control. No vendor advisory content indicates that the issue is already mitigated or requires no action.
CVE-2026-35361: CWE-281: Improper Preservation of Permissions in Uutils coreutils
Description
The mknod utility in uutils coreutils fails to handle security labels atomically by creating device nodes before setting the SELinux context. If labeling fails, the utility attempts cleanup using std::fs::remove_dir, which cannot remove device nodes or FIFOs. This leaves mislabeled nodes behind with incorrect default contexts, potentially allowing unauthorized access to device nodes that should have been restricted by mandatory access controls.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because the mknod utility in uutils coreutils does not atomically handle security labels when creating device nodes. Specifically, device nodes are created before the SELinux context is applied. If the labeling fails, the utility tries to clean up using std::fs::remove_dir, which cannot remove device nodes or FIFOs, resulting in leftover nodes with incorrect default security contexts. This improper preservation of permissions (CWE-281) can lead to unauthorized access to device nodes that should be restricted by SELinux mandatory access controls.
Potential Impact
The impact is limited to potential unauthorized access to device nodes due to incorrect SELinux labeling. The CVSS score of 3.4 (low severity) reflects limited confidentiality and integrity impact, requiring local privileges with high complexity and no user interaction. There is no indication of availability impact or known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — no official fix or patch links are provided. Users should monitor the vendor advisory for updates. Until a fix is available, cautious use of the mknod utility in uutils coreutils is advised, especially in environments relying on SELinux for mandatory access control. No vendor advisory content indicates that the issue is already mitigated or requires no action.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- canonical
- Date Reserved
- 2026-04-02T12:58:56.088Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e8f7d319fe3cd2cdd00cf9
Added to database: 4/22/2026, 4:31:15 PM
Last enriched: 4/22/2026, 4:49:07 PM
Last updated: 4/23/2026, 12:18:14 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.