CVE-2026-78409 Overview
CVE-2026-78409 affects the util-linux mount utility on Linux kernels 6.15 and later. The X-mount.subdir option takes a detached-tree fast path that calls open_tree() with the AT_SYMLINK_NOFOLLOW flag. That flag only suppresses following a symlink at the final component. It does not prevent intermediate symlink traversal, and it does not confine resolution to the newly mounted filesystem. A local unprivileged user holding an fstab-authorized X-mount.subdir entry can redirect the mount to an arbitrary host path at the intended mountpoint. The weakness is tracked as CWE-59: Improper Link Resolution Before File Access.
Critical Impact
A local user can attach any host directory in place of the intended subdirectory, exposing sensitive files and enabling privilege escalation through controlled mount content.
Affected Products
- util-linux mount utility using the X-mount.subdir option
- Linux kernel 6.15 and later where the detached-tree fast path is active
- Distributions shipping affected util-linux versions (see the Red Hat CVE-2026-78409 Advisory)
Discovery Timeline
- 2026-09-02 - CVE-2026-78409 published to the National Vulnerability Database
- 2026-09-02 - Last updated in NVD database
Technical Details for CVE-2026-78409
Vulnerability Analysis
The X-mount.subdir option instructs mount(8) to expose only a specified subdirectory of a source filesystem at the target mountpoint. On Linux 6.15 and later, util-linux takes a detached-tree fast path using the open_tree() syscall to obtain a handle to that subdirectory. The implementation passes AT_SYMLINK_NOFOLLOW in an attempt to block symlink abuse.
AT_SYMLINK_NOFOLLOW only affects the final path component. Intermediate path components are still resolved through symlinks. Resolution is also not confined to the source filesystem, so a symlink can redirect the lookup to any directory the kernel can reach. When the resulting file descriptor is used with move_mount(), the attacker-chosen directory is attached at the intended mountpoint.
Root Cause
The root cause is incorrect flag selection during path resolution. Safe confinement requires the OPEN_TREE_CLONE semantics combined with RESOLVE_BENEATH or RESOLVE_NO_SYMLINKS to keep resolution inside the newly mounted tree. Using only AT_SYMLINK_NOFOLLOW leaves a TOCTOU-adjacent gap where a user-writable component of the subdir path can be swapped for a symlink pointing outside the source filesystem.
Attack Vector
Exploitation requires a local unprivileged account and an fstab entry that grants the user permission to invoke mount with an X-mount.subdir option. The attacker replaces an intermediate directory in the configured subdir with a symlink that targets a sensitive host path such as /etc, /root, or a service data directory. When the authorized mount runs, that host path is bound at the mountpoint. The attacker then reads, modifies, or stages content that another user or root-owned service will trust. Refer to the GitHub Security Advisory GHSA-8f2p-47x3-43mv for upstream details.
Detection Methods for CVE-2026-78409
Indicators of Compromise
- Unexpected mount invocations by non-root users referencing X-mount.subdir in command lines or audit records.
- Mountpoints whose backing source resolves outside the declared filesystem after mount completes, visible in /proc/self/mountinfo.
- Symlinks appearing inside user-writable directories that are referenced by fstabX-mount.subdir entries.
Detection Strategies
- Audit execve events for /usr/bin/mount with arguments containing X-mount.subdir= and correlate the invoking UID against expected operators.
- Compare the pre-mount source path with the post-mount st_dev and mountinfo root field to detect filesystem escape.
- Alert on symlink creation inside directories referenced by user-authorized fstab entries.
Monitoring Recommendations
- Enable Linux Audit rules on mount, umount, open_tree, and move_mount syscalls with UID and command-line capture.
- Forward mount and fstab change events to a central analytics platform for correlation with account activity.
- Review /etc/fstab and /etc/fstab.d/ for entries granting user, users, or owner options combined with X-mount.subdir.
How to Mitigate CVE-2026-78409
Immediate Actions Required
- Inventory all fstab entries that combine X-mount.subdir with user-invokable mount options and disable them until patched.
- Apply vendor updates to util-linux as soon as fixed packages are published by your distribution.
- Restrict write access on directories that appear in X-mount.subdir paths to prevent symlink substitution.
Patch Information
Monitor the Red Hat CVE-2026-78409 Advisory and Red Hat Bug Report #2522607 for fixed package versions. The upstream fix is tracked in GitHub Security Advisory GHSA-8f2p-47x3-43mv and replaces the unsafe flag combination with resolution primitives that confine lookup to the source filesystem.
Workarounds
- Remove X-mount.subdir from user-authorized fstab entries and mount subdirectories from a privileged context instead.
- Place source filesystems that back X-mount.subdir mounts on paths that unprivileged users cannot modify.
- Where feasible, downgrade or pin kernels below 6.15 on hosts that cannot be patched, since the detached-tree fast path is not taken on earlier kernels.
# Configuration example: audit rule to log mount invocations with X-mount.subdir
-a always,exit -F arch=b64 -S execve -F path=/usr/bin/mount -k mount_subdir
# Review fstab for risky entries
grep -nE 'X-mount\.subdir|user(s)?|owner' /etc/fstab /etc/fstab.d/* 2>/dev/null
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

