CVE-2023-53197: USB: uhci: fix memory leak with using debugfs_lookup()

Published Sep 15, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

USB: uhci: 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 handles all of the logic at once.

Affected Software

129 affected componentsFixes available
Linux Foundation Linux Kernel
ubuntu/linux-hwe-edge*
ubuntu/linux-aws-5.0*
ubuntu/linux-aws-5.3*
ubuntu/linux-azure*
ubuntu/linux-azure-5.3*
ubuntu/linux-azure-edge*
ubuntu/linux-gcp*
ubuntu/linux-gcp-5.3*
ubuntu/linux-gke-4.15*
ubuntu/linux-gke-5.4*
ubuntu/linux-gkeop-5.4*
ubuntu/linux-hwe*
ubuntu/linux-hwe-edge*
ubuntu/linux-oem*
ubuntu/linux-oracle-5.0*
ubuntu/linux-oracle-5.3*
ubuntu/linux-aws-5.15<5.15.0-1041.46~20.04.1
5.15.0-1041.46~20.04.1
ubuntu/linux-azure-5.15<5.15.0-1045.52~20.04.1
5.15.0-1045.52~20.04.1
ubuntu/linux-gcp-5.15<5.15.0-1039.47~20.04.1
5.15.0-1039.47~20.04.1
ubuntu/linux-hwe-5.15<5.15.0-79.86~20.04.2
5.15.0-79.86~20.04.2
ubuntu/linux-ibm-5.15<5.15.0-1036.39~20.04.1
5.15.0-1036.39~20.04.1
ubuntu/linux-intel-iotg-5.15<5.15.0-1037.42~20.04.1
5.15.0-1037.42~20.04.1
ubuntu/linux-lowlatency-hwe-5.15<5.15.0-79.88~20.04.1
5.15.0-79.88~20.04.1
ubuntu/linux-nvidia-tegra-5.15<5.15.0-1016.16~20.04.1
5.15.0-1016.16~20.04.1
ubuntu/linux-oracle-5.15<5.15.0-1040.46~20.04.1
5.15.0-1040.46~20.04.1
ubuntu/linux-riscv-5.15<5.15.0-1038.42~20.04.2
5.15.0-1038.42~20.04.2
ubuntu/linux-aws-5.11*
ubuntu/linux-aws-5.13*
ubuntu/linux-aws-5.8*
ubuntu/linux-azure-5.11*
ubuntu/linux-azure-5.13*
ubuntu/linux-azure-5.8*
ubuntu/linux-azure-fde*
ubuntu/linux-gcp-5.11*
ubuntu/linux-gcp-5.13*
ubuntu/linux-gcp-5.8*
ubuntu/linux-gke*
ubuntu/linux-gke-5.15*
ubuntu/linux-gkeop*
ubuntu/linux-gkeop-5.15*
ubuntu/linux-hwe-5.11*
ubuntu/linux-hwe-5.13*
ubuntu/linux-hwe-5.8*
ubuntu/linux-intel-5.13*
ubuntu/linux-oem-5.10*
ubuntu/linux-oem-5.13*
ubuntu/linux-oem-5.6*
ubuntu/linux-oracle-5.11*
ubuntu/linux-oracle-5.13*
ubuntu/linux-oracle-5.8*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.11*
ubuntu/linux-riscv-5.8*
ubuntu/linux<5.15.0-79.86
5.15.0-79.86
ubuntu/linux-allwinner-5.19*
ubuntu/linux-aws<5.15.0-1042.47
5.15.0-1042.47
ubuntu/linux-aws-5.19*
ubuntu/linux-aws-6.2*
ubuntu/linux-aws-6.5*
ubuntu/linux-azure<5.15.0-1045.52
5.15.0-1045.52
ubuntu/linux-azure-5.19*
ubuntu/linux-azure-6.2*
ubuntu/linux-azure-6.5*
ubuntu/linux-azure-fde<5.15.0-1045.52.1
5.15.0-1045.52.1
ubuntu/linux-azure-fde-5.19*
ubuntu/linux-azure-fde-6.2*
ubuntu/linux-gcp<5.15.0-1039.47
5.15.0-1039.47
ubuntu/linux-gcp-5.19*
ubuntu/linux-gcp-6.2*
ubuntu/linux-gcp-6.5*
ubuntu/linux-gke<5.15.0-1039.44
5.15.0-1039.44
ubuntu/linux-gkeop<5.15.0-1025.30
5.15.0-1025.30
ubuntu/linux-hwe-5.19*
ubuntu/linux-hwe-6.2*
ubuntu/linux-hwe-6.5*
ubuntu/linux-ibm<5.15.0-1035.38
5.15.0-1035.38
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-intel-iotg<5.15.0-1037.42
5.15.0-1037.42
ubuntu/linux-kvm<5.15.0-1039.44
5.15.0-1039.44
ubuntu/linux-lowlatency<5.15.0-79.88
5.15.0-79.88
ubuntu/linux-lowlatency-hwe-5.19*
ubuntu/linux-lowlatency-hwe-6.2*
ubuntu/linux-lowlatency-hwe-6.5*
ubuntu/linux-nvidia<5.15.0-1030.30
5.15.0-1030.30
ubuntu/linux-nvidia-6.2*
ubuntu/linux-nvidia-6.5*
ubuntu/linux-nvidia-tegra<5.15.0-1016.16
5.15.0-1016.16
ubuntu/linux-nvidia-tegra-igx<5.15.0-1002.2
5.15.0-1002.2
ubuntu/linux-oem-5.17*
ubuntu/linux-oem-6.0*
ubuntu/linux-oem-6.1*
ubuntu/linux-oem-6.5*
ubuntu/linux-oracle<5.15.0-1040.46
5.15.0-1040.46
ubuntu/linux-oracle-6.5*
ubuntu/linux-raspi<5.15.0-1035.38
5.15.0-1035.38
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.19*
ubuntu/linux-riscv-6.5*
ubuntu/linux-starfive-5.19*
ubuntu/linux-starfive-6.2*
ubuntu/linux-starfive-6.5*
ubuntu/linux-xilinx-zynqmp<5.15.0-1025.29
5.15.0-1025.29
ubuntu/linux-bluefield<5.15.0-1022.24
5.15.0-1022.24
ubuntu/linux-intel-iot-realtime<5.15.0-1036.38
5.15.0-1036.38
ubuntu/linux-realtime<5.15.0-1043.48
5.15.0-1043.48
ubuntu/linux-fips*
ubuntu/linux-azure-6.11*
ubuntu/linux-gcp-6.11*
ubuntu/linux-hwe-6.11*
ubuntu/linux-intel*
ubuntu/linux-lowlatency-hwe-6.11*
ubuntu/linux-oem-6.11*
ubuntu/linux-oem-6.8*
ubuntu/linux-raspi-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
Linux Linux kernel<5.15.100
Linux Linux kernel>=5.16<6.1.18
Linux Linux kernel>=6.2<6.2.5
debian/linux<6.1.20-1
6.1.20-1
debian/linux<6.1.20-1
6.1.20-1
debian/linux<6.1.20-1
6.1.20-1
linux/kernel>=5.13.0<5.15.100
5.15.100
linux/kernel>=5.16.0<6.1.18
6.1.18
linux/kernel>=6.2.0<6.2.5
6.2.5
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1041.46~20.04.1
  2. Upgrade

    Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1045.52~20.04.1
  3. Upgrade

    Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1039.47~20.04.1
  4. Upgrade

    Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-79.86~20.04.2
  5. Upgrade

    Upgrade ubuntu/linux-ibm-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1036.39~20.04.1
  6. Upgrade

    Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1037.42~20.04.1
  7. Upgrade

    Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-79.88~20.04.1
  8. Upgrade

    Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1016.16~20.04.1
  9. Upgrade

    Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1040.46~20.04.1
  10. Upgrade

    Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1038.42~20.04.2
  11. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 5.15.0-79.86
  12. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 5.15.0-1042.47
  13. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 5.15.0-1045.52
  14. Upgrade

    Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.

    Fixed in 5.15.0-1045.52.1
  15. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 5.15.0-1039.47
  16. Upgrade

    Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.

    Fixed in 5.15.0-1039.44
  17. Upgrade

    Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.

    Fixed in 5.15.0-1025.30
  18. Upgrade

    Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.

    Fixed in 5.15.0-1035.38
  19. Upgrade

    Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.

    Fixed in 5.15.0-1037.42
  20. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 5.15.0-1039.44
  21. Upgrade

    Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.15.0-79.88
  22. Upgrade

    Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.

    Fixed in 5.15.0-1030.30
  23. Upgrade

    Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.

    Fixed in 5.15.0-1016.16
  24. Upgrade

    Upgrade ubuntu/linux-nvidia-tegra-igx to a version that resolves this vulnerability.

    Fixed in 5.15.0-1002.2
  25. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 5.15.0-1040.46
  26. Upgrade

    Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.

    Fixed in 5.15.0-1035.38
  27. Upgrade

    Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.

    Fixed in 5.15.0-1025.29
  28. Upgrade

    Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.

    Fixed in 5.15.0-1022.24
  29. Upgrade

    Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.

    Fixed in 5.15.0-1036.38
  30. Upgrade

    Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.

    Fixed in 5.15.0-1043.48
  31. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.20-1
  32. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 5.15.100
  33. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.1.18
  34. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.2.5
  35. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.15-1
  36. Configuration

    Replace calls to debugfs_lookup() with debugfs_lookup_and_remove() so the lookup result is properly released and the memory leak is avoided.

    Linux kernel USB UHCI debugfs handling debugfs lookup and removal = debugfs_lookup_and_remove()

Event History

Sep 15, 2025
CVE Published
via MITRE·02:06 PM
Data Sourced
via MITRE·02:06 PM
Description
Data Sourced
via OSV·02:06 PM
DescriptionAffected Software
Data Sourced
via OSV·02:15 PM
Severity
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2023-53197?

CVE-2023-53197 is classified as a medium severity vulnerability due to its potential impact on system stability over time.

2

How do I fix CVE-2023-53197?

To fix CVE-2023-53197, you should update to the latest version of the Linux kernel where the memory leak has been resolved.

3

What component of the system is affected by CVE-2023-53197?

CVE-2023-53197 affects the USB subsystem within the Linux kernel.

4

Is CVE-2023-53197 a newly discovered vulnerability?

CVE-2023-53197 has been recently resolved, indicating it is a newer vulnerability.

5

What can happen if CVE-2023-53197 is not addressed?

If CVE-2023-53197 is not addressed, it can lead to memory leaks, potentially affecting system performance over time.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203