🛡️ UBUNTU-CVE-2025-40105
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

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.

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-10-30
Updated 2026-06-15
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 6.17.0-14.14
linux-allwinner-5.19
linux-aws 6.17.0-1007.7
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1100.107~20.04.2
linux-aws-5.19
linux-aws-5.3
linux-aws-5.4
linux-aws-5.8
linux-aws-6.14
linux-aws-6.17 6.17.0-1007.7~24.04.1
linux-aws-6.2
linux-aws-6.5
linux-aws-6.8 6.8.0-1050.53~22.04.1
linux-aws-fips 6.8.0-1050.53+fips1
linux-azure 6.17.0-1008.8
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1110.119~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.4
linux-azure-5.8
linux-azure-6.11
linux-azure-6.14
linux-azure-6.2
linux-azure-6.5
linux-azure-6.8 6.8.0-1051.57~22.04.1
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.19
linux-azure-fde-6.14
linux-azure-fde-6.17
linux-azure-fde-6.2
linux-azure-fde-6.8
linux-azure-fips 6.8.0-1052.58+fips1
linux-azure-nvidia
linux-azure-nvidia-6.14
linux-bluefield
linux-fips 6.8.0-106.106+fips1
linux-gcp 6.17.0-1007.7
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1100.109~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.4
linux-gcp-5.8
linux-gcp-6.11
linux-gcp-6.14
linux-gcp-6.17 6.17.0-1008.8~24.04.1
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-6.8 6.8.0-1052.55~22.04.1
linux-gcp-fips 6.8.0-1052.55+fips1
linux-gke 6.8.0-1048.53
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 6.8.0-1035.38
linux-gkeop-5.15
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-170.180~20.04.3
linux-hwe-5.19
linux-hwe-5.4
linux-hwe-5.8
linux-hwe-6.11
linux-hwe-6.14
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-6.8 6.8.0-106.106~22.04.1
linux-hwe-edge
linux-ibm 6.8.0-1049.49
linux-ibm-5.15 5.15.0-1094.97~20.04.1
linux-ibm-5.4
linux-ibm-6.8 6.8.0-1049.49~22.04.1
linux-intel-5.13
linux-intel-iot-realtime 5.15.0-1092.94
linux-intel-iotg 5.15.0-1095.101
linux-intel-iotg-5.15 5.15.0-1095.101~20.04.1
linux-iot
linux-kvm 5.15.0-1092.97
linux-lowlatency 6.8.0-106.106.1
linux-lowlatency-hwe-5.15 5.15.0-170.180~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.11
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lowlatency-hwe-6.8 6.8.0-106.106.1~22.04.1
linux-nvidia 6.8.0-1049.52
linux-nvidia-6.11
linux-nvidia-6.17 6.17.0-1008.8
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-6.8 6.8.0-1049.52~22.04.1
linux-nvidia-lowlatency 6.8.0-1049.52.1
linux-nvidia-tegra 6.8.0-1020.20
linux-nvidia-tegra-5.15 5.15.0-1052.52~20.04.2
linux-nvidia-tegra-igx 5.15.0-1041.41
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.11
linux-oem-6.14
linux-oem-6.17 6.17.0-1011.11
linux-oem-6.5
linux-oem-6.8
linux-oracle 6.17.0-1007.7
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1097.103~20.04.1
linux-oracle-5.3
linux-oracle-5.4
linux-oracle-5.8
linux-oracle-6.14
linux-oracle-6.17 6.17.0-1007.7~24.04.1
linux-oracle-6.5
linux-oracle-6.8 6.8.0-1047.48~22.04.1
linux-raspi 6.17.0-1008.8
linux-raspi-5.4
linux-raspi-realtime 6.8.0-2040.41
linux-raspi2
linux-realtime 6.17.0-1006.7
linux-realtime-6.14
linux-realtime-6.17 6.17.0-1006.7~24.04.1
linux-realtime-6.8 6.8.1-1045.46~22.04.1
linux-riscv 6.17.0-14.14.1
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1095.99~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.14
linux-riscv-6.5
linux-riscv-6.8 6.8.0-106.106~22.04.1
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx 6.8.0-1028.29
linux-xilinx-zynqmp 5.15.0-1064.68

References

Similar Threats

Exploit Protection

Help block exploit attempts

BotEraser is designed to detect and help reduce malicious bot traffic that may target known vulnerabilities on your site.

Try BotEraser Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.