In the Linux kernel, the following vulnerability has been resolved: hwmon: Fix potential UAF in...

zetlyn/cve-ghsa vulnerability ghsa GHSA-xqgw-9m49-8xxh cve CVE-2026-98000 known 2026-09-25

https://github.com/advisories/GHSA-xqgw-9m49-8xxh

Properties

severityunknown
receipt
Source
GitHub advisories
Its words
unknown
Read by
field:severity
Said since
2026-09-28 11:44 UTC
Last answered
2026-10-06 13:46 UTC
Original
open at the source
What the source handed over
{
  "credits": [],
  "cve_id": "CVE-2026-98000",
  "cvss": {
    "score": null,
    "vector_string": null
  },
  "cvss_severities": {
    "cvss_v3": {
      "score": 0.0,
      "vector_string": null
    },
    "cvss_v4": {
      "score": 0.0,
      "vector_string": null
    }
  },
  "cwes": [],
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: Fix potential UAF in pec_store\n\nSashiko reports:\n\nIn pec_store(), a guard(mutex)(&hwdev->lock) is taken. If the chip write\noperation returns an error other than -EOPNOTSUPP, the code jumps to the\nput label, which calls put_device(hdev). If this drops the final reference,\nthe device is freed. When the function then returns, the guard cleanup\nfunction runs and attempts to unlock the freed mutex.\n\nUse scoped_guard() instead of guard() to avoid the problem.",
  "epss": {
    "percentage": 0.00166,
    "percentile": 0.05201
  },
  "ghsa_id": "GHSA-xqgw-9m49-8xxh",
  "github_reviewed_at": null,
  "html_url": "https://github.com/advisories/GHSA-xqgw-9m49-8xxh",
  "identifiers": [
    {
      "type": "GHSA",
      "value": "GHSA-xqgw-9m49-8xxh"
    },
    {
      "type": "CVE",
      "value": "CVE-2026-98000"
    }
  ],
  "nvd_published_at": "2026-09-25T11:17:28Z",
  "published_at": "2026-09-25T12:31:32Z",
  "references": [
    "https://nvd.nist.gov/vuln/detail/CVE-2026-98000",
    "https://git.kernel.org/stable/c/01dd8b4fc2cf83c66565c0f382fb1841e9000a89",
    "https://git.kernel.org/stable/c/354ccc99b2dc8ba0cf6d4de34e520bcf6ecca5c2",
    "https://git.kernel.org/stable/c/8afab57bcdbc2186f325972e777880ac5a220f4f",
    "https://github.com/advisories/GHSA-xqgw-9m49-8xxh"
  ],
  "repository_advisory_url": null,
  "severity": "unknown",
  "source_code_location": "",
  "summary": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: Fix potential UAF in...",
  "type": "unreviewed",
  "updated_at": "2026-09-25T12:31:37Z",
  "url": "https://api.github.com/advisories/GHSA-xqgw-9m49-8xxh",
  "vulnerabilities": [],
  "withdrawn_at": null
}

Text

In the Linux kernel, the following vulnerability has been resolved: hwmon: Fix potential UAF in... In the Linux kernel, the following vulnerability has been resolved: hwmon: Fix potential UAF in pec_store Sashiko reports: In pec_store(), a guard(mutex)(&hwdev->lock) is taken. If the chip write operation returns an error other than -EOPNOTSUPP, the code jumps to the put label, which calls put_device(hdev). If this drops the final reference, the device is freed. When the function then returns, the guard cleanup function runs and attempts to unlock the freed mutex. Use scoped_guard() instead of guard() to avoid the problem.