{
  "cveId": "CVE-2023-53054",
  "url": "https://patchblox.com/security/cve/CVE-2023-53054",
  "summary": "CVE-2023-53054 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-53054, released May 2, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  usb: dwc2: fix a devres leak in hw_enable upon s...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  usb: dwc2: fix a devres leak in hw_enable upon suspend resume  Each time the platform goes to low power, PM suspend / resume routines call: __dwc2_lowlevel_hw_enable -\u003E devm_add_action_or_reset(). This adds a new devres each time. This may also happen at runtime, as dwc2_lowlevel_hw_enable() can be called from udc_start().  This can be seen with tracing: - echo 1 \u003E /sys/kernel/debug/tracing/events/dev/devres_log/enable - go to low power - cat /sys/kernel/debug/tracing/trace  A new \u0022ADD\u0022 entry is found upon each low power cycle: ... devres_log: 49000000.usb-otg ADD 82a13bba devm_action_release (8 bytes) ... devres_log: 49000000.usb-otg ADD 49889daf devm_action_release (8 bytes) ...  A second issue is addressed here: - regulator_bulk_enable() is called upon each PM cycle (suspend/resume). - regulator_bulk_disable() never gets called.  So the reference count for these regulators constantly increase, by one upon each low power cycle, due to missing regulator_bulk_disable() call in __dwc2_lowlevel_hw_disable().  The original fix that introduced the devm_add_action_or_reset() call, fixed an issue during probe, that happens due to other errors in dwc2_driver_probe() -\u003E dwc2_core_reset(). Then the probe fails without disabling regulators, when dr_mode == USB_DR_MODE_PERIPHERAL.  Rather fix the error path: disable all the low level hardware in the error path, by using the \u0022hsotg-\u003Ell_hw_enabled\u0022 flag. Checking dr_mode has been introduced to avoid a dual call to dwc2_lowlevel_hw_disable(). \u0022ll_hw_enabled\u0022 should achieve the same (and is used currently in the remove() routine).",
  "published": "2025-05-02T16:15:24Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00206,
  "epssPercentile": 0.10631,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.25-1",
      "fix": "DEBIAN-CVE-2023-53054",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-53054",
      "released": "2025-05-02T16:15:24Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.1.25-1",
      "fix": "DEBIAN-CVE-2023-53054",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-53054",
      "released": "2025-05-02T16:15:24Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.1.25-1",
      "fix": "DEBIAN-CVE-2023-53054",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-53054",
      "released": "2025-05-02T16:15:24Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-10T01:44:33Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}