Vulnerability-Lookup

GHSA-43GV-WM7G-H6Q4

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:

thermal: hwmon: Remove hwmon class device along with its parent

The current code creates one hwmon device per thermal zone type and that device is registered under the first thermal zone of the given type.

That turns out to be problematic when the thermal zone holding the hwmon device is removed.

For example, say that there are two ACPI thermal zones on a system

/sys/devices/virtual/thermal/thermal_zone0/ /sys/devices/virtual/thermal/thermal_zone1/

The current code registers a hwmon class device for thermal_zone0 only:

/sys/devices/virtual/thermal/thermal_zone0/hwmon0/

because the type is "acpitz" for both of them, but it adds a sysfs attribute that belongs to thermal_zone1 under it:

/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input

There is also

/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input

which belongs to thermal_zone0.

When thermal_zone0 is removed, say because the ACPI thermal driver is unbound from the underlying platform device, thermal_remove_hwmon_sysfs() skips the removal of hwmon0 because of the temp2_input attribute belonging to thermal_zone1 which effectively prevents thermal_zone0 removal from making progress.

Address this by making thermal_remove_hwmon_sysfs() remove the entire hwmon class device interface for the given thermal zone type when the thermal zone device holding it is removed.

To prevent races with thermal_add_hwmon_sysfs() that may interfere with this, carry out the entire addition and removal of hwmon sysfs interfaces for thermal zones under thermal_hwmon_list_lock.

Also adjust the layout of the labels in thermal_add_hwmon_sysfs() to the current kernel coding style to align with the new "unlock" label.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-90311"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-17T17:17:28Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nthermal: hwmon: Remove hwmon class device along with its parent\n\nThe current code creates one hwmon device per thermal zone type and that\ndevice is registered under the first thermal zone of the given type.\n\nThat turns out to be problematic when the thermal zone holding the\nhwmon device is removed.\n\nFor example, say that there are two ACPI thermal zones on a system\n\n /sys/devices/virtual/thermal/thermal_zone0/\n /sys/devices/virtual/thermal/thermal_zone1/\n\nThe current code registers a hwmon class device for thermal_zone0 only:\n\n /sys/devices/virtual/thermal/thermal_zone0/hwmon0/\n\nbecause the type is \"acpitz\" for both of them, but it adds a sysfs\nattribute that belongs to thermal_zone1 under it:\n\n /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input\n\nThere is also\n\n /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input\n\nwhich belongs to thermal_zone0.\n\nWhen thermal_zone0 is removed, say because the ACPI thermal driver is\nunbound from the underlying platform device, thermal_remove_hwmon_sysfs()\nskips the removal of hwmon0 because of the temp2_input attribute\nbelonging to thermal_zone1 which effectively prevents thermal_zone0\nremoval from making progress.\n\nAddress this by making thermal_remove_hwmon_sysfs() remove the entire\nhwmon class device interface for the given thermal zone type when the\nthermal zone device holding it is removed.\n\nTo prevent races with thermal_add_hwmon_sysfs() that may interfere\nwith this, carry out the entire addition and removal of hwmon sysfs\ninterfaces for thermal zones under thermal_hwmon_list_lock.\n\nAlso adjust the layout of the labels in thermal_add_hwmon_sysfs() to\nthe current kernel coding style to align with the new \"unlock\" label.",
  "id": "GHSA-43gv-wm7g-h6q4",
  "modified": "2026-09-17T18:32:00Z",
  "published": "2026-09-17T18:32:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90311"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2b57e24d34b2dfc43c81942bb359d6315bf302fb"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-90311 (GCVE-0-2026-90311)

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

Title

thermal: hwmon: Remove hwmon class device along with its parent

Summary

In the Linux kernel, the following vulnerability has been resolved: thermal: hwmon: Remove hwmon class device along with its parent The current code creates one hwmon device per thermal zone type and that device is registered under the first thermal zone of the given type. That turns out to be problematic when the thermal zone holding the hwmon device is removed. For example, say that there are two ACPI thermal zones on a system /sys/devices/virtual/thermal/thermal_zone0/ /sys/devices/virtual/thermal/thermal_zone1/ The current code registers a hwmon class device for thermal_zone0 only: /sys/devices/virtual/thermal/thermal_zone0/hwmon0/ because the type is "acpitz" for both of them, but it adds a sysfs attribute that belongs to thermal_zone1 under it: /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input There is also /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input which belongs to thermal_zone0. When thermal_zone0 is removed, say because the ACPI thermal driver is unbound from the underlying platform device, thermal_remove_hwmon_sysfs() skips the removal of hwmon0 because of the temp2_input attribute belonging to thermal_zone1 which effectively prevents thermal_zone0 removal from making progress. Address this by making thermal_remove_hwmon_sysfs() remove the entire hwmon class device interface for the given thermal zone type when the thermal zone device holding it is removed. To prevent races with thermal_add_hwmon_sysfs() that may interfere with this, carry out the entire addition and removal of hwmon sysfs interfaces for thermal zones under thermal_hwmon_list_lock. Also adjust the layout of the labels in thermal_add_hwmon_sysfs() to the current kernel coding style to align with the new "unlock" label.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/4fa8915f40f744c6d…
https://git.kernel.org/stable/c/2b57e24d34b2dfc43…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 , < 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4 (git) Affected: f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 , < 2b57e24d34b2dfc43c81942bb359d6315bf302fb (git)
Linux	Linux	Affected: 4.19 Unaffected: 0 , < 4.19 (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/thermal/thermal_hwmon.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4",
              "status": "affected",
              "version": "f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5",
              "versionType": "git"
            },
            {
              "lessThan": "2b57e24d34b2dfc43c81942bb359d6315bf302fb",
              "status": "affected",
              "version": "f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/thermal/thermal_hwmon.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.19"
            },
            {
              "lessThan": "4.19",
              "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": "4.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "4.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nthermal: hwmon: Remove hwmon class device along with its parent\n\nThe current code creates one hwmon device per thermal zone type and that\ndevice is registered under the first thermal zone of the given type.\n\nThat turns out to be problematic when the thermal zone holding the\nhwmon device is removed.\n\nFor example, say that there are two ACPI thermal zones on a system\n\n /sys/devices/virtual/thermal/thermal_zone0/\n /sys/devices/virtual/thermal/thermal_zone1/\n\nThe current code registers a hwmon class device for thermal_zone0 only:\n\n /sys/devices/virtual/thermal/thermal_zone0/hwmon0/\n\nbecause the type is \"acpitz\" for both of them, but it adds a sysfs\nattribute that belongs to thermal_zone1 under it:\n\n /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input\n\nThere is also\n\n /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input\n\nwhich belongs to thermal_zone0.\n\nWhen thermal_zone0 is removed, say because the ACPI thermal driver is\nunbound from the underlying platform device, thermal_remove_hwmon_sysfs()\nskips the removal of hwmon0 because of the temp2_input attribute\nbelonging to thermal_zone1 which effectively prevents thermal_zone0\nremoval from making progress.\n\nAddress this by making thermal_remove_hwmon_sysfs() remove the entire\nhwmon class device interface for the given thermal zone type when the\nthermal zone device holding it is removed.\n\nTo prevent races with thermal_add_hwmon_sysfs() that may interfere\nwith this, carry out the entire addition and removal of hwmon sysfs\ninterfaces for thermal zones under thermal_hwmon_list_lock.\n\nAlso adjust the layout of the labels in thermal_add_hwmon_sysfs() to\nthe current kernel coding style to align with the new \"unlock\" label."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-17T16:08:31.645Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4"
        },
        {
          "url": "https://git.kernel.org/stable/c/2b57e24d34b2dfc43c81942bb359d6315bf302fb"
        }
      ],
      "title": "thermal: hwmon: Remove hwmon class device along with its parent",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90311",
    "datePublished": "2026-09-17T16:08:31.645Z",
    "dateReserved": "2026-09-11T19:38:34.800Z",
    "dateUpdated": "2026-09-17T16:08:31.645Z",
    "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.

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.

Action not permitted

GHSA-43GV-WM7G-H6Q4

CVE-2026-90311 (GCVE-0-2026-90311)

Tags

Sightings

Nomenclature

Related by attack behaviour