FKIE_CVE-2026-99718

Vulnerability from fkie_nvd - Published: 2026-11-20 06:18 - Updated: 2026-11-20 06:18
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind When a peci_dimmtemp device is unbound concurrently with its delayed initialization work (detect_work), newly allocated devm resources and the hwmon device are leaked, leading to a use-after-free when reading the lingering hwmon sysfs attributes. In peci_dimmtemp_probe(), detect_work is registered for cancellation via devm_delayed_work_autocancel(). During driver detach, devres_release_all() first moves all existing entries from dev->devres_head onto a local todo list before invoking their release callbacks in reverse order. If create_dimm_temp_info_delayed() is already running when devm_delayed_work_drop() calls cancel_delayed_work_sync(), create_dimm_temp_info() can allocate dimmtemp_label strings via devm_kzalloc()/devm_kasprintf() and register the hwmon device via devm_hwmon_device_register_with_info(), appending new devres entries to the now-empty dev->devres_head. Once the work finishes, devres_release_all() frees priv and priv->name from the local todo list without re-evaluating dev->devres_head, leaving the late devres allocations and registered hwmon device behind with a dangling priv pointer. Cancel detect_work synchronously in a driver .remove() callback instead of relying on devm_delayed_work_autocancel() so that the work is fully drained before devres_release_all() detaches dev->devres_head, allowing any devm resources registered by the delayed work to be released in proper reverse order. Also only schedule detect_work when check_populated_dimms() returns -EAGAIN so that probe failure paths do not leave delayed work pending.
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/hwmon/peci/dimmtemp.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f27cb64b04af01370fbe2d23ba9aeb3401d6def8",
              "status": "affected",
              "version": "73bc1b885daeb684fbcd16cc4e979cac6a831b12",
              "versionType": "git"
            },
            {
              "lessThan": "c7dcea6bdc6c36c649c1fdd29909b232bcac28c9",
              "status": "affected",
              "version": "73bc1b885daeb684fbcd16cc4e979cac6a831b12",
              "versionType": "git"
            },
            {
              "lessThan": "3f6bd7aeea5c3bd5ced9e23184155065f551ea96",
              "status": "affected",
              "version": "73bc1b885daeb684fbcd16cc4e979cac6a831b12",
              "versionType": "git"
            },
            {
              "lessThan": "61bc4514b8e99e9733c04de028885f6fc906d628",
              "status": "affected",
              "version": "73bc1b885daeb684fbcd16cc4e979cac6a831b12",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/hwmon/peci/dimmtemp.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.18"
            },
            {
              "lessThan": "5.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.118",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.64",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind\n\nWhen a peci_dimmtemp device is unbound concurrently with its delayed\ninitialization work (detect_work), newly allocated devm resources and\nthe hwmon device are leaked, leading to a use-after-free when reading\nthe lingering hwmon sysfs attributes.\n\nIn peci_dimmtemp_probe(), detect_work is registered for cancellation via\ndevm_delayed_work_autocancel(). During driver detach, devres_release_all()\nfirst moves all existing entries from dev-\u003edevres_head onto a local todo\nlist before invoking their release callbacks in reverse order. If\ncreate_dimm_temp_info_delayed() is already running when\ndevm_delayed_work_drop() calls cancel_delayed_work_sync(),\ncreate_dimm_temp_info() can allocate dimmtemp_label strings via\ndevm_kzalloc()/devm_kasprintf() and register the hwmon device via\ndevm_hwmon_device_register_with_info(), appending new devres entries to\nthe now-empty dev-\u003edevres_head. Once the work finishes,\ndevres_release_all() frees priv and priv-\u003ename from the local todo list\nwithout re-evaluating dev-\u003edevres_head, leaving the late devres\nallocations and registered hwmon device behind with a dangling priv\npointer.\n\nCancel detect_work synchronously in a driver .remove() callback instead\nof relying on devm_delayed_work_autocancel() so that the work is fully\ndrained before devres_release_all() detaches dev-\u003edevres_head, allowing\nany devm resources registered by the delayed work to be released in\nproper reverse order. Also only schedule detect_work when\ncheck_populated_dimms() returns -EAGAIN so that probe failure paths do\nnot leave delayed work pending."
    }
  ],
  "id": "CVE-2026-99718",
  "lastModified": "2026-11-20T06:18:08.363",
  "metrics": {},
  "published": "2026-11-20T06:18:08.363",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/3f6bd7aeea5c3bd5ced9e23184155065f551ea96"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/61bc4514b8e99e9733c04de028885f6fc906d628"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/c7dcea6bdc6c36c649c1fdd29909b232bcac28c9"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f27cb64b04af01370fbe2d23ba9aeb3401d6def8"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.