mknod: Device nodes created mislabeled on SELinux, with broken cleanup (remove_dir on a node)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.4 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-35361: 0.14% estimated exploitation activity in the next 30 days; percentile 3.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

uutils calls mknod before setting the SELinux context (GNU uses setfscreatecon first, labeling atomically). If setselinuxsecuritycontext fails, cleanup uses std::fs::removedir, which cannot remove device nodes or FIFOs, leaving the mislabeled node behind. Impact: on SELinux-enforcing systems the node is created with the wrong context; the command reports failure but leaves a mislabeled device node that may bypass mandatory access control, and orphaned nodes can persist across reboots. Recommendation: use setfscreatecon before mknod, abort on failure, and use removefile for cleanup. Remediation: Acknowledged by Canonical. --- Reported by Zellic in the uutils coreutils Program Security Assessment (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.58. Credit: Zellic.

Published by the source

6 Jul 2026, 21:54 UTC

Last modified by the source

6 Jul 2026, 21:54 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r9hw-mj3w-phcq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35361

Advisory: mknod: Device nodes created mislabeled on SELinux, with broken cleanup (remove_dir on a node)
IDs: CVE-2026-35361, GHSA-r9hw-mj3w-phcq
Record: https://patchnext.com/advisories/cve-2026-35361 (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: uu_mknod 0.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io uu_mknod: affected < 0.6.0; fixed in 0.6.0

## Suggested inspection (read-only)
- crates.io uu_mknod: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on uu_mknod.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r9hw-mj3w-phcq (GitHub-reviewed advisory GHSA-r9hw-mj3w-phcq lists affected ranges: crates.io uu_mknod >=0 <0.6.0)

Commands are suggestions: review each one before running it.