CVE-2023-53408Published Sep 18, 2025 · Sep 18Updated 2d ago
trace/blktrace: fix memory leak with using debugfs_lookup()
Linux
Medium5.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
trace/blktrace: fix memory leak with using debugfs_lookup()
When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once.
From the CVE record · Linux
The Linux kernel's trace/blktrace component can leak memory over time because a result from debugfs_lookup() is not released. The input does not specify how an attacker could trigger the leak or whether access, authentication, or user interaction is required.
Engineers running Linux kernels should check their exposure; affected versions are not specified.