{
  "id": "CVE-2026-93116",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-93116",
  "published_at": "2026-09-17T16:11:23.852Z",
  "title": "platform/x86: asus-wmi: fix resource leaks on probe failure",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: asus-wmi: fix resource leaks on probe failure\n\nDuring driver initialization in asus_wmi_add(), various subsystems are\nregistered sequentially. However, the error path labels are out of order\nrelative to the registration sequence.\n\nSpecifically:\n1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to\n   fail_custom_fan_curve. Because this label is placed below fail_sysfs,\n   it bypasses the cleanup calls for the input device and sysfs groups,\n   which were successfully registered before, leaking those resources.\n2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad.\n   Because fail_screenpad is placed below fail_backlight, it bypasses the\n   cleanup calls for backlight and rfkill, leaking those resources.\n\nFix these resource leaks by reordering the error path labels in\nasus_wmi_add() to match the exact reverse order of the resource\nallocations.",
  "cvss_by_source": {
    "cna": 7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 0f0ac158d28ff78e75c334e869b1cb8e69372a1f, \u003c 72d792c8053f238ae541fdaa90e609548509b65f",
          "\u003e= 0f0ac158d28ff78e75c334e869b1cb8e69372a1f, \u003c 959ed35f8c8f07b8dd43c3f917a43ae2f77e4471",
          "\u003e= 0f0ac158d28ff78e75c334e869b1cb8e69372a1f, \u003c 8d5999608da60db45949e5459f74f581cdaacd04",
          "\u003e= 0f0ac158d28ff78e75c334e869b1cb8e69372a1f, \u003c 8410cd2690d463b60527d00ac8cffea2d5a041f6",
          "\u003e= 0f0ac158d28ff78e75c334e869b1cb8e69372a1f, \u003c 3308b8c5f5a28403611a2f5a46f06aabe4f0c661",
          "\u003e= 0f0ac158d28ff78e75c334e869b1cb8e69372a1f, \u003c ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95"
        ],
        "fixed_in": [
          "72d792c8053f238ae541fdaa90e609548509b65f",
          "959ed35f8c8f07b8dd43c3f917a43ae2f77e4471",
          "8d5999608da60db45949e5459f74f581cdaacd04",
          "8410cd2690d463b60527d00ac8cffea2d5a041f6",
          "3308b8c5f5a28403611a2f5a46f06aabe4f0c661",
          "ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "5.17"
        ],
        "fixed_in": [
          "0",
          "6.1.191",
          "6.6.160",
          "6.12.114",
          "6.18.57",
          "7.2.6",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 72d792c8053f238ae541fdaa90e609548509b65f or 959ed35f8c8f07b8dd43c3f917a43ae2f77e4471 or 8d5999608da60db45949e5459f74f581cdaacd04 or 8410cd2690d463b60527d00ac8cffea2d5a041f6 or 3308b8c5f5a28403611a2f5a46f06aabe4f0c661 or ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95 or later.",
      "Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.114 or 6.18.57 or 7.2.6 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
