Advisory

GHSA-r9hw-mj3w-phcq

Also known as: CVE-2026-35361

Summary

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

Details

uutils calls mknod *before* setting the SELinux context (GNU uses setfscreatecon first, labeling atomically). If set_selinux_security_context fails, cleanup uses std::fs::remove_dir, 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 remove_file 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._

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-07-06 21:54 UTC
Modified
2026-07-06 22:11 UTC

Affected packages and fixes

uu_mknod

crates.io · All systems

Affected

  • introduced 0, fixed 0.6.0 (semver)

Fixed versions

0.6.0

Fix

  • Fixed version 0.6.0
    cargo update -p uu_mknod --precise 0.6.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences