staging: pi433: fix memory leak with using debugfs_lookup()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.186.2.56.3In the Linux kernel, the following vulnerability has been resolved:
staging: pi433: 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. This requires saving off the root directory dentry to make creation of individual device subdirectories easier.
From the CVE record · Linux
The Linux kernel’s staging pi433 component leaks memory over time because a debugfs lookup result 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 with the staging pi433 component should check whether their kernel includes the fix; affected versions are not specified.