CVE-2023-53413 USB: isp116x: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: isp116x: 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-53413

CVE-2023-53413 concerns a memory leak in the Linux kernel USB isp116x driver triggered by debugfs_lookup() usage. The issue arises because the result from debugfs_lookup() must be released with dput(), and if not, memory leaks accrue over time. The referenced fix replaces the call path with debug...

CVE-2023-53412 USB: gadget: bcm63xx_udc: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: gadget: bcm63xxudc: 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 debugfslookupandremo...

CVE-2023-53412 USB: gadget: bcm63xx_udc: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: gadget: bcm63xxudc: 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 debugfslookupandremo...

CVE-2023-53411 PM: EM: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: PM: EM: 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 which...

CVE-2023-53411 PM: EM: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: PM: EM: 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 which...

CVE-2023-53410 USB: ULPI: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: ULPI: 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 whi...

CVE-2023-53410 USB: ULPI: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: ULPI: 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 whi...

CVE-2023-53411

CVE-2023-53411 affects the Linux kernel. The issue is a memory leak when using debugfs_lookup(), because the returned object must be released with dput(). The documented fix is to use debugfs_lookup_and_remove() which handles the required cleanup in one step. Exploitation details are not provided...

CVE-2023-53411 PM: EM: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: PM: EM: 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 which...

CVE-2023-53410

In the Linux kernel, the following vulnerability has been resolved: USB: ULPI: 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 whi...

CVE-2023-53410 USB: ULPI: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: ULPI: 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 whi...

CVE-2023-53411

In the Linux kernel, the following vulnerability has been resolved: PM: EM: 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 which...

CVE-2023-53409 drivers: base: component: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: drivers: base: component: 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...

CVE-2023-53409

In the Linux kernel, the following vulnerability has been resolved: drivers: base: component: 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...

CVE-2023-53409 drivers: base: component: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: drivers: base: component: 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...

CVE-2023-53408

CVE-2023-53408 affects the Linux kernel’s trace/blktrace path. The issue is a memory leak when using debugfs_lookup(); the returned object must be dput()’d, otherwise memory leaks accumulate. The documented fix simplifies handling by replacing the call with debugfs_lookup_and_remove(), which perf...

CVE-2023-53408 trace/blktrace: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: trace/blktrace: 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 instea...

CVE-2023-53408 trace/blktrace: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: trace/blktrace: 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 instea...

CVE-2023-53408 trace/blktrace: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: trace/blktrace: 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 instea...