Bug 2522684 (CVE-2026-78410) - CVE-2026-78410 util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection
Summary: CVE-2026-78410 util-linux: util-linux: restricted bind mounts do not pin the ...
Keywords:
Status: NEW
Alias: CVE-2026-78410
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-24 18:48 UTC by OSIDB Bzimport
Modified: 2026-09-02 14:09 UTC (History)
25 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-24 18:48:56 UTC
Restricted-user bind/rbind mounts authorize the source from /etc/fstab but do not pin that source inode before the privileged mount. libmount later opens the source as a pathname via open_tree(AT_FDCWD, source, OPEN_TREE_CLONE|...) (mnt_context_open_tree in context.c / hook_mount.c). A local unprivileged user who can replace the fstab bind source or a writable ancestor with a symlink can redirect SUID mount(8) to bind an attacker-selected host directory. When the same fstab entry includes X-mount.owner=, X-mount.group=, or X-mount.mode=, hook_owner.c then applies root-privileged fchownat()/chmod() to the mounted root, which for a bind mount is the redirected source inode. This is a source-side pathname TOCTOU; current HEAD already pins the target and uses fd-based owner hooks (the CVE-2026-53612 target-path fix), but that fd now refers to the attacker-redirected bind source. Distinct from the public loop backing-file TOCTOU and from CVE-2026-76642 (failed external helper still running post-hooks). X-mount.owner/group/mode was introduced with v2.39; no upstream fix as of 2026-08-24. Reported upstream by Alex0Young. GHSA-rh77-686x-2f2m.


Note You need to log in before you can comment on or make changes to this bug.