Skip to main content
VulnerabilityPublished

CVE-2026-99718: Linux kernel · hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99718· High

Not known to be exploited · fixed in f27cb64b04af01370fbe2d23ba9aeb3401d6def8 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f27cb64b04af01370fbe2d23ba9aeb3401d6def8, c7dcea6bdc6c36c649c1fdd29909b232bcac28c9, 61bc4514b8e99e9733c04de028885f6fc906d628 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to f27cb64b04af01370fbe2d23ba9aeb3401d6def8, c7dcea6bdc6c36c649c1fdd29909b232bcac28c9, 61bc4514b8e99e9733c04de028885f6fc906d628 or 3f6bd7aeea5c3bd5ced9e23184155065f551ea96.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 73bc1b885daeb684fbcd16cc4e979cac6a831b12, < f27cb64b04af01370fbe2d23ba9aeb3401d6def8
Fixed in
  • f27cb64b04af01370fbe2d23ba9aeb3401d6def8
LinuxLinuxAffected
  • ≥ 73bc1b885daeb684fbcd16cc4e979cac6a831b12, < c7dcea6bdc6c36c649c1fdd29909b232bcac28c9
Fixed in
  • c7dcea6bdc6c36c649c1fdd29909b232bcac28c9
LinuxLinuxAffected
  • ≥ 73bc1b885daeb684fbcd16cc4e979cac6a831b12, < 61bc4514b8e99e9733c04de028885f6fc906d628
Fixed in
  • 61bc4514b8e99e9733c04de028885f6fc906d628
LinuxLinuxAffected
  • ≥ 73bc1b885daeb684fbcd16cc4e979cac6a831b12, < 3f6bd7aeea5c3bd5ced9e23184155065f551ea96
Fixed in
  • 3f6bd7aeea5c3bd5ced9e23184155065f551ea96
LinuxLinuxAffected
  • =5.18
Fixed in–

Description

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.

References

Community reviews

Loading reviews…