Memory Leak Vulnerability in Linux Kernel - CVE-2025-40105

linux Updated 04 Jun 2026

Summary

30/10/2025
N/A
No i
Unrated
Not published

DEBIAN-CVE-2025-40105: 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... Affects linux versions 5.10.103-1 – 6.9.9-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux kernel is the core component of many operating systems, providing the essential interface between hardware and software. It manages system resources, including memory, processes, and device drivers. This vulnerability arises from a flaw in the Virtual File System (VFS) layer, which can lead to memory leaks under certain conditions, particularly when handling disconnected dentries during unmount operations.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified where disconnected dentries may not be properly marked during unmount operations. When a user calls open_by_handle_at() on an inode that is not cached, a disconnected dentry is created. If this dentry is a directory and the reconnection process fails, a new dentry is created under the parent without marking the original as disconnected. This inconsistency can lead to memory leaks, as the dentry remains in memory and may cause the 'Busy inodes after unmount' bug if unmount is called before memory reclamation occurs.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. However, users are advised to monitor their systems for any unusual behavior related to file operations and to ensure that they are running the latest kernel version.

Conclusion

The CVE-2025-40105 vulnerability in the Linux kernel poses a risk of memory leaks due to improper handling of disconnected dentries. Users are encouraged to update their systems to the latest patched versions to mitigate this risk. Regular monitoring and timely updates are essential for maintaining system security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2025-40105 is a vulnerability in the Linux kernel that can lead to memory leaks due to improper handling of disconnected dentries during unmount operations.

This vulnerability can cause memory leaks, leading to potential system instability and the 'Busy inodes after unmount' bug, which may prevent proper unmounting of filesystems.

If you are using Debian 11, 12, 13, or 14 with the Linux kernel, your system may be affected. It is recommended to check for updates and apply the latest patches.

You can use Vulert, a tool that monitors open-source vulnerabilities in your software. By simply uploading your manifest file like package-lock.json, you can check for vulnerabilities without needing to install any software.

While there are no specific workarounds, it is advisable to monitor your system for any unusual behavior and plan to update your kernel as soon as possible.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback