Linux Kernel Memory Leak Vulnerability in Debugfs Lookup Handling

Vulnerability

A memory leak vulnerability has been addressed in the Linux kernel related to the improper management of debugfs_lookup() results. If the result of debugfs_lookup() is not followed by a dput() call, it can lead to a gradual memory leak. The vulnerability exists in the stable versions of the Linux kernel. The recommended practice is to use debugfs_lookup_and_remove(), which automatically manages the necessary operations, thereby preventing the memory leak.

Impact

The vulnerability can cause a gradual memory leak, potentially leading to increased memory usage over time.

Reproduction

The vulnerability can be reproduced by calling debugfs_lookup() without subsequently calling dput() on the result. This omission will cause memory to leak over time. The issue can be observed in the component_debugfs_del() function, where debugfs_remove(debugfs_lookup(dev_name(m->parent), component_debugfs_dir)) is used. This can be replaced with debugfs_lookup_and_remove(dev_name(m->parent), component_debugfs_dir) to prevent the memory leak.

Remediation

The vulnerability has been fixed in the Linux kernel stable tree. Users can upgrade to the latest version to address this issue.

Added: Sep 18, 2025, 2:34 PM
Updated: Sep 18, 2025, 2:34 PM

Vulnerability Rating

Custom Algorithm
spread
9.0
impact
0.6
exploitability
4.3
remediation
7.7
relevance
0.5
threat
4.8
urgency
2.9
incentive
1.7

Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.