CVE-2026-99718

published 20 Nov 2026 · updated 21 Nov 2026

hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind

4.1MediumCVSS 4.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f27cb64b04af01370fbe2d23ba9aeb3401d6def8, Kernel 3f6bd7aeea5c3bd5ced9e23184155065f551ea96, Kernel 61bc4514b8e99e9733c04de028885f6fc906d628 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=73bc1b885daeb684fbcd16cc4e979cac6a831b12 <f27cb64b04af01370fbe2d23ba9aeb3401d6def8, >=73bc1b885daeb684fbcd16cc4e979cac6a831b12 <3f6bd7aeea5c3bd5ced9e23184155065f551ea96, >=73bc1b885daeb684fbcd16cc4e979cac6a831b12 <61bc4514b8e99e9733c04de028885f6fc906d628, >=73bc1b885daeb684fbcd16cc4e979cac6a831b12 <c7dcea6bdc6c36c649c1fdd29909b232bcac28c9, =5.18f27cb64b04af01370fbe2d23ba9aeb3401d6def8, 3f6bd7aeea5c3bd5ced9e23184155065f551ea96, 61bc4514b8e99e9733c04de028885f6fc906d628, c7dcea6bdc6c36c649c1fdd29909b232bcac28c9
linux-kernel: Kernel>=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=5.18.0 <6.12.1186.18.64, 7.3.5, 6.12.118

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99718 severity on Zeptric[![CVE-2026-99718](https://zeptric.io/badge/cve/CVE-2026-99718.svg)](https://zeptric.io/cve/CVE-2026-99718)