CVE-2023-53403

CVE-2023-53403: Linux kernel vulnerability in time/debug causing potential memory leak when using debugfs_lookup(). The issue arises because the result of debugfs_lookup() must be dput()-ed; if not, memory leaks occur over time. The documented mitigation is to replace the call with debugfs_lookup...

CVE-2023-53404 USB: fotg210: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: fotg210: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...

CVE-2023-53403 time/debug: Fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: time/debug: Fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...

CVE-2023-53404

In the Linux kernel, the following vulnerability has been resolved: USB: fotg210: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...

CVE-2023-53404 USB: fotg210: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: fotg210: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...

CVE-2023-53403

In the Linux kernel, the following vulnerability has been resolved: time/debug: Fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...

CVE-2023-53403 time/debug: Fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: time/debug: Fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...

CVE-2023-53402 kernel/printk/index.c: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: kernel/printk/index.c: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove...

CVE-2023-53402

In the Linux kernel, the following vulnerability has been resolved: kernel/printk/index.c: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove...

CVE-2023-53402 kernel/printk/index.c: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: kernel/printk/index.c: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove...

CVE-2023-53402 kernel/printk/index.c: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: kernel/printk/index.c: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove...

CVE-2023-53402

CVE-2023-53402 affects the Linux kernel, specifically the printk debugfs path. The root cause is a memory leak in kernel/printk/index.c when using debugfs_lookup() without a matching dput(). The documented fix replaces the sequence with debugfs_lookup_and_remove(), handling the logic and preventi...

CVE-2022-50400

The CVE-2022-50400 issue concerns the Linux kernel greybus: audio_helper code, where debugfs usage was removed due to incorrect handling that could leak memory and even erase all debugfs entries. The fix is to remove all debugfs logic from the audio_helper code; if needed later, a fix for the inc...

CVE-2022-50400 staging: greybus: audio_helper: remove unused and wrong debugfs usage

In the Linux kernel, the following vulnerability has been resolved: staging: greybus: audiohelper: remove unused and wrong debugfs usage In the greybus audiohelper code, the debugfs file for the dapm has the potential to be removed and memory will be leaked. There is also the very real potential...

CVE-2022-50400

In the Linux kernel, the following vulnerability has been resolved: staging: greybus: audiohelper: remove unused and wrong debugfs usage In the greybus audiohelper code, the debugfs file for the dapm has the potential to be removed and memory will be leaked. There is also the very real potential...

CVE-2022-50400 staging: greybus: audio_helper: remove unused and wrong debugfs usage

In the Linux kernel, the following vulnerability has been resolved: staging: greybus: audiohelper: remove unused and wrong debugfs usage In the greybus audiohelper code, the debugfs file for the dapm has the potential to be removed and memory will be leaked. There is also the very real potential...

CVE-2022-50400 staging: greybus: audio_helper: remove unused and wrong debugfs usage

In the Linux kernel, the following vulnerability has been resolved: staging: greybus: audiohelper: remove unused and wrong debugfs usage In the greybus audiohelper code, the debugfs file for the dapm has the potential to be removed and memory will be leaked. There is also the very real potential...

CVE-2023-53390 drivers: base: dd: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove...

CVE-2023-53390 drivers: base: dd: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove...

CVE-2023-53390 drivers: base: dd: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove...