CVE-2026-98981
High · 8.8CVSS
8.8
EPSS
0.2%
Published
Oct 23, 2026
CISA due date
—
Cloudanix analysis
A flaw in how the Linux kernel handles file deletions while files are hidden by mounts in different environments can let local users peek at files they should not see.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Moderate
- Impact
- Privilege Gain
- Component
- OS kernel
- Class
- Race Condition
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Race condition in __detach_mounts() during unlink/rmdir/rename leaves dentry hashed and positive between detach_mounts() and d_delete(), allowing lockless or reference-count lookups in other mount namespaces to observe and access files whose mounts have been detached.
Why it matters to the business
Attackers with local access can read files that should remain hidden by mount namespaces, risking exposure of secrets or data in multi-tenant, container, or bind-mount environments; high CVSS and recent publication warrant prompt kernel updates despite low EPSS.
How an attack unfolds
Attacker in a cloned mount namespace keeps a reference to an overmounted file; while the driver unlinks the mountpoint in the original namespace, the attacker performs repeated lockless lookups that succeed in the brief window after detach_mounts() but before d_delete(), reading the underlying file contents.
How to fix it
Apply the upstream fix that calls d_drop() on the dentry before detach_mounts() in __detach_mounts(); rebuild and deploy updated Linux kernels; monitor kernel changelogs for the stable backports addressing the dentry hash ordering issue.
How to confirm the fix worked
Confirm the patched kernel contains the d_drop() call ahead of detach_mounts() in fs/namespace.c; reproduce the unlink_covered test program and verify that walkers no longer observe the secret file contents after the mount is detached.
Typical attack path
- Obtain or create a mount namespace containing a bind mount over a target file
- Trigger unlink/rmdir/rename on the mountpoint from another namespace while holding the dentry reference
- Perform concurrent lockless lookups (e.g., openat2 with RESOLVE_CACHED) that race the detach window
- Read file contents that should have been covered by the mount
How to detect it
Monitor kernel audit logs and syscall traces for rapid sequences of unlink followed by open/read operations on the same path from multiple namespaces; look for processes using open_tree or move_mount syscalls combined with high-frequency lookup attempts.
What your security team should do
- Prioritize kernel upgrades on systems using mount namespaces, containers, or bind mounts within the next patching cycle
- Review and restrict unprivileged mount namespace creation where feasible
- Add kernel version checks to vulnerability scanners and asset inventories
The record
In the Linux kernel, the following vulnerability has been resolved: namespace: unhash a dentry before detaching the mounts on it unlink(), rmdir() and rename() remove the entry from the filesystem, call detach_mounts() on the entry with the inode locked and then call d_delete() once the inode is unlocked. The thing is that between detach_mounts() and d_delete() the dentry is still hashed and positive. But after detach_mounts() nothing covers the dentry anymore. A lookup that finds this dentry in the dcache can uncover what the mounts hid. That's a problem when unlinking files or directories that are mountpoints in other mount namespaces. Everybody who had the underlying entry covered can race the detach_mount() call until d_delete() has run. The race window isn't all that small. It encompasses namespace_unlock() with a full synchronize_rcu_expedited() grace period and the inode_unlock() of the entry. In my experiments three walkers that kept trying read an overmounted file in 11938 of the 16140 unlinks that removed its mountpoint from a bind mount of the filesystem within a minute. Fun fact, d_invalidate() has the same ordering problem but gets it right. It unhashes the dentry first and detaches the mounts afterwards. Let's do the same in __detach_mounts(): - A lookup that hasn't found the dentry yet misses it in the dcache and waits for the directory lock that the caller holds until the name is gone for good. - A lockless lookup that found it already fails the mount_lock check while the dentry still counts as a mountpoint and the d_seq check once it doesn't, and retries. This fixes the lockless path. We still need to fix the reference count lookup in a follow-up patch. So d_drop() the dentry. The dentry stays positive and held but can't be found anymore. Then proceed with the detach and unlink. Reproducer: The reads were counted with the program below, three walkers for 60 s in a VM with 4 CPUs. The race window is stretched with the debug patch pasted here. fs.detach_race_walk_us sleeps in lookup_fast() once it found a mountpoint dentry and before its mounts are crossed. fs.detach_race_unlink_us sleeps in vfs_unlink() between detach_mounts() and d_delete(). // SPDX-License-Identifier: GPL-2.0 /* * unlink_covered: unlink a file that is a mountpoint in a detached copy of * its mount, against lookups that open it through that copy. * * A is a tmpfs with the file f1 (content SECRET_F) and the plain file * MARK_A. A' is an open_tree(OPEN_TREE_CLONE) copy of A with MARK_A bound * on A'/f1, held through an O_PATH fd on its root once the tree fd is * closed. Walkers open f1 through that fd while the driver unlinks A/f1, * where nothing is mounted on it. A walker may read MARK_A or get ENOENT. * A read of SECRET_F is a hit: the name was found after its mount was * gone. The lockless walks use openat2(RESOLVE_CACHED). * * usage: unlink_covered [-t seconds] [-w walkers] */ #ifndef _GNU_SOURCE #define _GNU_SOURCE #endif #include <errno.h> #include <fcntl.h> #include <pthread.h> #include <stdatomic.h> #include <stdio.h> #include <stdlib.h> #include <string.h> #include <unistd.h> #include <sys/mount.h> #include <sys/stat.h> #include <sys/syscall.h> #include <linux/openat2.h> #ifndef __NR_open_tree #define __NR_open_tree 428 #endif #ifndef __NR_move_mount #define __NR_move_mount 429 #endif #ifndef __NR_openat2 #define __NR_openat2 437 #endif #ifndef OPEN_TREE_CLONE #define OPEN_TREE_CLONE 1 #endif #ifndef OPEN_TREE_CLOEXEC #define OPEN_TREE_CLOEXEC O_CLOEXEC #endif #ifndef MOVE_MOUNT_F_EMPTY_PATH #define MOVE_MOUNT_F_EMPTY_PATH 0x00000004 #endif #define WORK "/tmp/uc" #define ADIR WORK "/A" static int duration = 60, nwalkers = 3; static atomic_int stop, writer_waiting; static pthread_rwlock_t cur_lock = PTHREAD_RWLOCK_INITIALIZER; static int cur_fd = -1; /* the root of A', -1 wh ---truncated---
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|