Lucene search
+L

1817 matches found

CVE
CVE
added 2025/09/18 1:58 p.m.38 views

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...

5.5CVSS6.2AI score0.00135EPSS
SaveExploits0References4Affected Software1
Vulnrichment
Vulnrichment
added 2025/09/18 1:58 p.m.3 views

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...

6.2AI score0.00136EPSS
SaveExploits0References4
CVE
CVE
added 2025/09/18 1:58 p.m.33 views

CVE-2023-53412

The CVE-2023-53412 issue affects the Linux kernel USB gadget bcm63xx_udc where memory leaks occur when using debugfs_lookup() because the result is not dput()’d. The mitigated pattern is to call debugfs_lookup_and_remove() which handles the lookup and cleanup in one step, preventing leaks. Eviden...

5.5CVSS6.2AI score0.00136EPSS
SaveExploits0References4Affected Software1
Cvelist
Cvelist
added 2025/09/18 1:58 p.m.20 views

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...

0.00136EPSS
SaveExploits0References4
OSV
OSV
added 2025/09/18 1:58 p.m.6 views

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...

5.5CVSS6.2AI score
SaveExploits0References7
Vulnrichment
Vulnrichment
added 2025/09/18 1:58 p.m.2 views

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...

6.2AI score0.00134EPSS
SaveExploits0References3
Vulnrichment
Vulnrichment
added 2025/09/18 1:58 p.m.2 views

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...

6.2AI score0.00135EPSS
SaveExploits0References5
CVE
CVE
added 2025/09/18 1:58 p.m.34 views

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...

5.5CVSS6.2AI score0.00135EPSS
SaveExploits0References5Affected Software1
Cvelist
Cvelist
added 2025/09/18 1:58 p.m.14 views

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...

0.00135EPSS
SaveExploits0References5
OSV
OSV
added 2025/09/18 1:58 p.m.3 views

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...

5.5CVSS5AI score
SaveExploits0References8
OSV
OSV
added 2025/09/18 1:58 p.m.8 views

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...

5.5CVSS6.2AI score
SaveExploits0References6
Debian CVE
Debian CVE
added 2025/09/18 1:58 p.m.32 views

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...

5.5CVSS5.4AI score0.00134EPSS
SaveExploits0
CVE
CVE
added 2025/09/18 1:58 p.m.33 views

CVE-2023-53410

CVE-2023-53410 (Linux kernel) : The issue is a memory leak in USB ULPI related to using debugfs_lookup() without proper dput() on the result. The recommended remediation is to replace the call with debugfs_lookup_and_remove(), which handles lookup and cleanup in one step. Affected context and ref...

5.5CVSS6.2AI score0.00134EPSS
SaveExploits0References3Affected Software1
Debian CVE
Debian CVE
added 2025/09/18 1:58 p.m.4 views

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...

5.5CVSS5.4AI score0.00135EPSS
SaveExploits0
Cvelist
Cvelist
added 2025/09/18 1:58 p.m.9 views

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...

0.00135EPSS
SaveExploits0References4
Debian CVE
Debian CVE
added 2025/09/18 1:58 p.m.7 views

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...

5.5CVSS5.4AI score0.00135EPSS
SaveExploits0
CVE
CVE
added 2025/09/18 1:58 p.m.33 views

CVE-2023-53409

The CVE-2023-53409 issue concerns the Linux kernel: when using debugfs_lookup(), the returned object must be released with dput() to prevent a memory leak. The advisories state a fix by using debugfs_lookup_and_remove(), which handles the necessary logic in one step, mitigating the memory leak. A...

5.5CVSS6.2AI score0.00135EPSS
SaveExploits0References4Affected Software1
OSV
OSV
added 2025/09/18 1:58 p.m.6 views

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...

5.5CVSS6.2AI score
SaveExploits0References7
Cvelist
Cvelist
added 2025/09/18 1:58 p.m.13 views

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...

0.00135EPSS
SaveExploits0References4
CVE
CVE
added 2025/09/18 1:58 p.m.33 views

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...

5.5CVSS6.2AI score0.00135EPSS
SaveExploits0References4Affected Software1
Rows per page
Query Builder