{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.10-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  power: supply: max77705: Free allocated workqueue and fix removal order  Use devm interface for allocating workqueue to fix two bugs at the same time:  1. Driver leaks the memory on remove(), because the workqueue is not    destroyed.  2. Driver allocates workqueue and then registers interrupt handlers    with devm interface.  This means that probe error paths will not use a    reversed order, but first destroy the workqueue and then, via devm    release handlers, free the interrupt.     The interrupt handler schedules work on this exact workqueue, thus if    interrupt is hit in this short time window - after destroying    workqueue, but before devm() frees the interrupt - the schedulled    work will lead to use of freed memory.  Change is not equivalent in the workqueue itself: use non-legacy API which does not set (__WQ_LEGACY | WQ_MEM_RECLAIM).  The workqueue is used to update power supply (power_supply_changed()) status, thus there is no point to run it for memory reclaim.  Note that dev_name() is not directly used in second argument to prevent possible unlikely parsing any \"%\" character in device name as format.",
  "id": "DEBIAN-CVE-2026-53308",
  "modified": "2026-09-14T16:47:46.169556303Z",
  "published": "2026-06-26T20:17:24.110Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-53308"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-53308"
  ]
}