Vulnerability-Lookup

GHSA-JVJX-CFGV-JW7V

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-wireless: Fail probe when there is no ACPI match

Every platform driver can be forced to match a device that does not match its list of device IDs because of device_match_driver_override(), so platform drivers that rely on the existence of a device ACPI companion object need to verify its presence.

asus_wireless_probe() returns success when acpi_match_acpi_device() finds no match, leaving behind an input device that never reports anything because the notify handler is not installed. Worse, when the driver is force-bound to a device without an ACPI companion, probe still succeeds and stores a NULL companion pointer, which asus_wireless_remove() later passes to acpi_dev_remove_notify_handler(), leading to a NULL pointer dereference on unbind.

Return -ENODEV when the device does not match the ID table. This also covers the missing-companion case, because acpi_match_acpi_device() rejects a NULL device. Perform the check before allocating any driver state, instead of after the input device has already been registered.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-93124"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-17T17:18:07Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: asus-wireless: Fail probe when there is no ACPI match\n\nEvery platform driver can be forced to match a device that does not match\nits list of device IDs because of device_match_driver_override(), so\nplatform drivers that rely on the existence of a device ACPI companion\nobject need to verify its presence.\n\nasus_wireless_probe() returns success when acpi_match_acpi_device()\nfinds no match, leaving behind an input device that never reports\nanything because the notify handler is not installed.  Worse, when the\ndriver is force-bound to a device without an ACPI companion, probe\nstill succeeds and stores a NULL companion pointer, which\nasus_wireless_remove() later passes to acpi_dev_remove_notify_handler(),\nleading to a NULL pointer dereference on unbind.\n\nReturn -ENODEV when the device does not match the ID table.  This also\ncovers the missing-companion case, because acpi_match_acpi_device()\nrejects a NULL device.  Perform the check before allocating any driver\nstate, instead of after the input device has already been registered.",
  "id": "GHSA-jvjx-cfgv-jw7v",
  "modified": "2026-09-17T18:32:11Z",
  "published": "2026-09-17T18:32:11Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93124"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4aefd66ef7822cf7d3f53146dcee0b71021ed2b7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7bfa711f311a584002e16ecd750627306deb805c"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-93124 (GCVE-0-2026-93124)

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

Title

platform/x86: asus-wireless: Fail probe when there is no ACPI match

Summary

In the Linux kernel, the following vulnerability has been resolved: platform/x86: asus-wireless: Fail probe when there is no ACPI match Every platform driver can be forced to match a device that does not match its list of device IDs because of device_match_driver_override(), so platform drivers that rely on the existence of a device ACPI companion object need to verify its presence. asus_wireless_probe() returns success when acpi_match_acpi_device() finds no match, leaving behind an input device that never reports anything because the notify handler is not installed. Worse, when the driver is force-bound to a device without an ACPI companion, probe still succeeds and stores a NULL companion pointer, which asus_wireless_remove() later passes to acpi_dev_remove_notify_handler(), leading to a NULL pointer dereference on unbind. Return -ENODEV when the device does not match the ID table. This also covers the missing-companion case, because acpi_match_acpi_device() rejects a NULL device. Perform the check before allocating any driver state, instead of after the input device has already been registered.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/7bfa711f311a58400…
https://git.kernel.org/stable/c/4aefd66ef7822cf7d…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: f7e648027d7e1b5c06eb86d944b7e23926254cee , < 7bfa711f311a584002e16ecd750627306deb805c (git) Affected: f7e648027d7e1b5c06eb86d944b7e23926254cee , < 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7 (git)
Linux	Linux	Affected: 7.1 Unaffected: 0 , < 7.1 (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-wireless.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7bfa711f311a584002e16ecd750627306deb805c",
              "status": "affected",
              "version": "f7e648027d7e1b5c06eb86d944b7e23926254cee",
              "versionType": "git"
            },
            {
              "lessThan": "4aefd66ef7822cf7d3f53146dcee0b71021ed2b7",
              "status": "affected",
              "version": "f7e648027d7e1b5c06eb86d944b7e23926254cee",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/platform/x86/asus-wireless.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "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": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: asus-wireless: Fail probe when there is no ACPI match\n\nEvery platform driver can be forced to match a device that does not match\nits list of device IDs because of device_match_driver_override(), so\nplatform drivers that rely on the existence of a device ACPI companion\nobject need to verify its presence.\n\nasus_wireless_probe() returns success when acpi_match_acpi_device()\nfinds no match, leaving behind an input device that never reports\nanything because the notify handler is not installed.  Worse, when the\ndriver is force-bound to a device without an ACPI companion, probe\nstill succeeds and stores a NULL companion pointer, which\nasus_wireless_remove() later passes to acpi_dev_remove_notify_handler(),\nleading to a NULL pointer dereference on unbind.\n\nReturn -ENODEV when the device does not match the ID table.  This also\ncovers the missing-companion case, because acpi_match_acpi_device()\nrejects a NULL device.  Perform the check before allocating any driver\nstate, instead of after the input device has already been registered."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-17T16:11:29.223Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7bfa711f311a584002e16ecd750627306deb805c"
        },
        {
          "url": "https://git.kernel.org/stable/c/4aefd66ef7822cf7d3f53146dcee0b71021ed2b7"
        }
      ],
      "title": "platform/x86: asus-wireless: Fail probe when there is no ACPI match",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-93124",
    "datePublished": "2026-09-17T16:11:29.223Z",
    "dateReserved": "2026-09-17T16:02:15.087Z",
    "dateUpdated": "2026-09-17T16:11:29.223Z",
    "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.