Vulnerability · Published Oct 30, 2025 · Assigned by Linux

CVE-2025-40105vfs: Don't leak disconnected dentries on umount

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 94.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: vfs: Don't leak disconnected dentries on umount When user calls open_by_handle_at() on some inode that is not cached, we will create disconnected dentry for it. If such dentry is a directory, exportfs_decode_fh_raw() will then try to connect this dentry to the dentry tree through reconnect_path(). It may happen for various reasons (such as corrupted fs or race with rename) that the call to lookup_one_unlocked() in reconnect_one() will fail to find the dentry we are trying to reconnect and instead create a new dentry under the parent. Now this dentry will not be marked as disconnected although the parent still may well be disconnected (at least in case this inconsistency happened because the fs is corrupted and .. doesn't point to the real parent directory). This creates inconsistency in disconnected flags but AFAICS it was mostly harmless. At least until commit f1ee616214cb ("VFS: don't keep disconnected dentries on d_anon") which removed adding of most disconnected dentries to sb->s_anon list. Thus after this commit cleanup of disconnected dentries implicitely relies on the fact that dput() will immediately reclaim such dentries. However when some leaf dentry isn't marked as disconnected, as in the scenario described above, the reclaim doesn't happen and the dentries are "leaked". Memory reclaim can eventually reclaim them but otherwise they stay in memory and if umount comes first, we hit infamous "Busy inodes after unmount" bug. Make sure all dentries created under a disconnected parent are marked as disconnected as well.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.158-1DEBIAN-CVE-2025-40105
Debian:13linux6.12.57-1DEBIAN-CVE-2025-40105
Debian:14linux6.17.6-1DEBIAN-CVE-2025-40105
Ubuntu:22.04:LTSlinux5.15.0-170.180UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux6.8.0-106.106UBUNTU-CVE-2025-40105
Ubuntu:25.10linux6.17.0-14.14UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-aws5.15.0-1100.107UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-aws6.8.0-1050.53UBUNTU-CVE-2025-40105
Ubuntu:25.10linux-aws6.17.0-1007.7UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1050.53~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-azure6.8.0-1051.57UBUNTU-CVE-2025-40105
Ubuntu:25.10linux-azure6.17.0-1008.8UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1058.65UBUNTU-CVE-2025-40105
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-gcp5.15.0-1100.109UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-gcp6.8.0-1052.55UBUNTU-CVE-2025-40105
Ubuntu:25.10linux-gcp6.17.0-1007.7UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1008.8~24.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-gke5.15.0-1096.102UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-gke6.8.0-1048.53UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1083.91UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1035.38UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-106.106~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-ibm5.15.0-1094.97UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-ibm6.8.0-1049.49UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1049.49~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1095.101UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-kvm5.15.0-1092.97UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-170.180UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-106.106.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-106.106.1~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1095.96UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1049.52UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1008.8UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1049.52~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1049.52.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1052.52UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1020.20UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1041.41UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1011.11UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-oracle5.15.0-1097.103UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-oracle6.8.0-1047.48UBUNTU-CVE-2025-40105
Ubuntu:25.10linux-oracle6.17.0-1007.7UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1047.48~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-raspi5.15.0-1097.100UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-raspi6.8.0-1050.54UBUNTU-CVE-2025-40105
Ubuntu:25.10linux-raspi6.17.0-1008.8UBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-40105
Ubuntu:25.10linux-realtime6.17.0-1006.7UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-40105
Ubuntu:25.10linux-riscv6.17.0-14.14.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-106.106~22.04.1UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-40105
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1028.29UBUNTU-CVE-2025-40105
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1064.68UBUNTU-CVE-2025-40105

Affected products (as reported)

VendorProductVersions
Linux Linux f1ee616214cb22410e939d963bbb2349c2570f02 – before b5abafd0aa8d7bcb935c8f91e4cfc2f2820759e4f1ee616214cb22410e939d963bbb2349c2570f02 – before 20863bb7fbb016379f8227122edfabc5c799bc79f1ee616214cb22410e939d963bbb2349c2570f02 – before 8004d4b8cbf1bd68a23c160d57287e177c82cc69f1ee616214cb22410e939d963bbb2349c2570f02 – before 7e0c8aaf4e28918abded547a5147c7d52c4af7d2f1ee616214cb22410e939d963bbb2349c2570f02 – before cebfbf40056a4d858b2a3ca59a69936d599bd209f1ee616214cb22410e939d963bbb2349c2570f02 – before 620f3b0ede9c5cb4976cd0457d0b04ad551e5d6bf1ee616214cb22410e939d963bbb2349c2570f02 – before eadc49999fa994d6fbd70c332bd5d5051cc42261f1ee616214cb22410e939d963bbb2349c2570f02 – before 56094ad3eaa21e6621396cc33811d8f72847a834
Linux Linux 4.16

References