Vulnerability-Lookup

GHSA-5872-JRXC-47C3

Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32

Details

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

platform/x86: asus-wmi: fix resource leaks on probe failure

During driver initialization in asus_wmi_add(), various subsystems are registered sequentially. However, the error path labels are out of order relative to the registration sequence.

Specifically: 1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to fail_custom_fan_curve. Because this label is placed below fail_sysfs, it bypasses the cleanup calls for the input device and sysfs groups, which were successfully registered before, leaking those resources. 2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad. Because fail_screenpad is placed below fail_backlight, it bypasses the cleanup calls for backlight and rfkill, leaking those resources.

Fix these resource leaks by reordering the error path labels in asus_wmi_add() to match the exact reverse order of the resource allocations.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-93116"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-17T17:18:06Z",
    "severity": null
  },
  "details": "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.",
  "id": "GHSA-5872-jrxc-47c3",
  "modified": "2026-09-17T18:32:11Z",
  "published": "2026-09-17T18:32:11Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93116"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3308b8c5f5a28403611a2f5a46f06aabe4f0c661"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-93116 (GCVE-0-2026-93116)

Vulnerability from cvelistv5 – Published: 2026-09-17 16:11 – Updated: 2026-09-17 16:11

Title

platform/x86: asus-wmi: fix resource leaks on probe failure

Summary

In the Linux kernel, the following vulnerability has been resolved: platform/x86: asus-wmi: fix resource leaks on probe failure During driver initialization in asus_wmi_add(), various subsystems are registered sequentially. However, the error path labels are out of order relative to the registration sequence. Specifically: 1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to fail_custom_fan_curve. Because this label is placed below fail_sysfs, it bypasses the cleanup calls for the input device and sysfs groups, which were successfully registered before, leaking those resources. 2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad. Because fail_screenpad is placed below fail_backlight, it bypasses the cleanup calls for backlight and rfkill, leaking those resources. Fix these resource leaks by reordering the error path labels in asus_wmi_add() to match the exact reverse order of the resource allocations.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/3308b8c5f5a284036…
https://git.kernel.org/stable/c/ef3daa2b84a2b8499…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 0f0ac158d28ff78e75c334e869b1cb8e69372a1f , < 3308b8c5f5a28403611a2f5a46f06aabe4f0c661 (git) Affected: 0f0ac158d28ff78e75c334e869b1cb8e69372a1f , < ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95 (git)
Linux	Linux	Affected: 5.17 Unaffected: 0 , < 5.17 (semver) Unaffected: 7.2.6 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/platform/x86/asus-wmi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "3308b8c5f5a28403611a2f5a46f06aabe4f0c661",
              "status": "affected",
              "version": "0f0ac158d28ff78e75c334e869b1cb8e69372a1f",
              "versionType": "git"
            },
            {
              "lessThan": "ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95",
              "status": "affected",
              "version": "0f0ac158d28ff78e75c334e869b1cb8e69372a1f",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/platform/x86/asus-wmi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.17"
            },
            {
              "lessThan": "5.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.6",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-17T16:11:23.852Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/3308b8c5f5a28403611a2f5a46f06aabe4f0c661"
        },
        {
          "url": "https://git.kernel.org/stable/c/ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95"
        }
      ],
      "title": "platform/x86: asus-wmi: fix resource leaks on probe failure",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-93116",
    "datePublished": "2026-09-17T16:11:23.852Z",
    "dateReserved": "2026-09-17T16:02:15.086Z",
    "dateUpdated": "2026-09-17T16:11:23.852Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.