GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-3HCM-7XPR-63QG

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32
VLAI
Details

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

hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero

Sashiko reports:

In the aspeed-g6-pwm-tacho driver, the aspeed_tach_val_to_rpm() function calculates the fan RPM using the tachometer value. However, it does not check if the tachometer value is zero before performing the division.

If the hardware reports a tachometer value of 0 (which can happen due to an extremely fast pulse, a stuck edge, or a hardware glitch), the calculated tach_div evaluates to 0. The subsequent call to do_div() with tach_div as the divisor triggers a divide-by-zero exception, leading to a kernel panic.

Check the divisor against zero to fix the problem.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-72394"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:12Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero\n\nSashiko reports:\n\nIn the aspeed-g6-pwm-tacho driver, the aspeed_tach_val_to_rpm() function\ncalculates the fan RPM using the tachometer value. However, it does not\ncheck if the tachometer value is zero before performing the division.\n\nIf the hardware reports a tachometer value of 0 (which can happen due to\nan extremely fast pulse, a stuck edge, or a hardware glitch), the\ncalculated tach_div evaluates to 0. The subsequent call to do_div() with\ntach_div as the divisor triggers a divide-by-zero exception, leading to\na kernel panic.\n\nCheck the divisor against zero to fix the problem.",
  "id": "GHSA-3hcm-7xpr-63qg",
  "modified": "2026-08-15T06:32:23Z",
  "published": "2026-08-15T06:32:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72394"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/898ca04b096b9e4640300eab91468c826a1ec92b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a3f98bd397398e2d4a7f98e006b5aaf4d54ebdf3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fb8a5afe6f1f8aa7f19c6dda23d277dd6ae5d9e1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fe87b8dc67f1b2c64e76a66e78468c533d3c44ca"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…