CVE-2026-35376: chcon: recursive relabel not anchored to traversal dirfd (TOCTOU)

Medium CVSS 4.5

OSV id
GHSA-9rv8-9hvg-92mq
Also known as
CVE-2026-35376
Published
Last modified

Affected packages

PackageAffected versionsFixed in
uu_chcon
Cargo
< 0.10.0 0.10.0

How to fix it

Upgrade uu_chcon to 0.10.0 or later.

cargo update -p uu_chcon --precise 0.10.0
  • If it is an indirect dependency, `cargo update -p` still works; if a parent crate pins an older version, upgrade that crate.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

chcon resolved recursive targets from fts_accpath with a fresh path lookup, so traversal and the SELinux get/set were not bound to traversal directory state. A privileged recursive relabel can be redirected to unintended objects under rename/symlink races. Fix opens targets with openat against the traversal cwd fd before the SELinux operation.

Fixed in 0.10.0 (PR #12566, commit 7cfc74e47ffab452663be6842d788a5164d9688b): recursive relabel resolution is anchored to the traversal dirfd.


Zellic private finding (zellic-ext/coreutils-private PR #120). Reported in the Zellic uutils coreutils Program Security Assessment (for Canonical, Jan 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.